Release Notes

● Issue 36–157172: After you modify the Data Retrieval Schedule settings, Event Posting Level settings are cleared.
Resolution: Reconfigure the Event Posting Level settings.
Version Affected: 5.0 and later
● Issue 37–156357: Firmware remediation from vSphere Lifecycle Manager fails on host having iDRAC version lower than
2.70.70 and IDSDM component.
The support for IDSDM firmware update is introduced from iDRAC firmware version 2.70.70. When the machine gets
updated to 2.70.70, it will notice the presence of IDSDM and with older firmware. If you are managing cluster having iDRAC
version lower than 2.70.70 and IDSDM component using vSphere Lifecycle Manager, the host remains in non-complaint after
firmware remediation.
Resolution: Perform the remediation operation twice. Alternatively, you can use the firmware update functionality from
OMIVV to update the iDRAC to 2.70.70, and then use the vSphere Lifecycle Manager flow.
Version Affected: 5.1
● Issue 38–159900: Unable to view the proper remediation failure message in vSphere Lifecycle Manager.
When remediation of a host fails, the vSphere Lifecycle Manager displays "Unknown Message" instead of proper message
sent from OMIVV. This is a limitation in vCenter 7.0. For more information, see the VMware documentation.
Resolution: See the OMIVV logs for proper failure message.
Version Affected: 5.1
● Issue 39–160776: Unable to associate the cluster profile deleted and created using the same name in vSphere Lifecycle
Manager.
This issue occur when the cluster profile associated with vSphere Lifecycle Manager image is deleted and if you create the
new cluster profile with the same name and try to associate the new cluster profile to vSphere Lifecycle Manager image.
Resolution: Create a cluster profile with different name and associate the same in vSphere Lifecycle Manager image.
Version Affected: 5.1
● Issue 40–162621: Unable to downgrade the MX chassis firmware using OMIVV
If you downgrade MX chassis firmware from higher version to lower using OMIVV, OMIVV shows the job as In Progress for
a long time (up to 6 hrs) and eventually reports failure of downgrade operation. But, the downgrade operation is successfully
completed.
Resolution: Downgrade firmware using OME-Modular.
Version Affected: 5.1
14
Known issues