Gen9 blades and VC Mgr Major error 6030 - Profile Pending

[Steve_Tippett]

Can anyone share knowledge of the root cause(s) of the VC Manager Major error 6030 - "Profile could not be assigned to powered up server".   I got bit by this recently while doing Virtual Connect firmware upgrades (HP VC Flex-10/10D Module - firmware 4.45 to 4.50) and several servers dropped off the network after the interconnect modules reset.   Reviewing the VC Manager system log shows 6030 Major error - while the VCSU log doesn't indicate any issues with the firmware upgrade itself.   Power-cycling the affected servers brings them back on the network, but a firmware upgrade on the interconnect modules should be non-impacting to the servers if the server profiles provide redundant network ports and the server O/S properly handles the temporary link loss on each port.

-----------------------------------------------------------------------
Record    : 3136
Date/Time : 2017-10-06 01:04:26-04:00
Info      : PRO:ServerProfileBay10:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 10
-----------------------------------------------------------------------
Record    : 3137
Date/Time : 2017-10-06 01:04:29-04:00
Info      : PRO:ServerProfileBay11:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 11
-----------------------------------------------------------------------
Record    : 3138
Date/Time : 2017-10-06 01:04:32-04:00
Info      : PRO:ServerProfileBay12:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 12
-----------------------------------------------------------------------
Record    : 3139
Date/Time : 2017-10-06 01:04:34-04:00
Info      : PRO:ServerProfileBay15:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 15
-----------------------------------------------------------------------