Release Notes

Known issues
Topics:
Template deployment configuration job not created for sled
Service tag of IOM is reported incorrectly from OME-Modular after reset all
Multi-chassis firmware rollback fails with error
Deployment and Configuration Job created multiple times for some sleds during Quick Deploy and Attach operation for sleds
Error while assigning identities
Unable to log in to OME-Modular Web interface after performing factory reset
OME-Modular takes up to 30 minutes to fetch network IOM inventory
Member chassis storage sleds inventory for all drives displayed as encryption capable in lead chassis
HTTPS custom port in OME-Modular does not work after upgrading to 1.10.00 or later
Identity pool options missing in Edit Network view and during deployment
Member chassis displays error message on promoted lead chassis
Template deployment configuration job not created
for sled
Description
Template deployment configuration job is not created for a sled that is removed and reinserted after the
backup lead is promoted. The job is not created because profiles are attached to the occupied slots from
the original lead.
Workaround Detach and reattach the required profiles for the occupied slots after backup lead is promoted and before
removing or reinserting the sleds.
Systems affected iDRAC, PowerEdge MX740c, and PowerEge MX840c
Tracking number 145969
Service tag of IOM is reported incorrectly from OME-
Modular after reset all
Description
OME-Modular reports a blank service tag for the IOMs after a reset all, racadm racresetcfg,
operation.
Workaround Perform management module reset or failover.
Systems affected All systems supported in this release.
Tracking number 142890
Multi-chassis firmware rollback fails with error
Description
When you try firmware rollback for compute device components on the member chassis, with
components rollback source as Device, from the MCM group lead, a job is created on the member
chassis and the job fails.
Workaround You can roll back firmware with the source as "Device" directly on the respective member chassis.
Systems affected PowerEdge MX7000
6
12 Known issues