Release Notes

• Issue: ASM-3862 : UEFI boot is not supported in ASM.
Description : The BIOS boot mode does not change to UEFI after the local
hard drive is set as the target boot device. This issue occurs because ASM
does not support UEFI boot support.
Resolution/Workaround : None
• Issue: ASM-4123 : Service reports "Error" state though all other components are successful.
Description : In some cases when deleting a failed resource, for example, a
VM Component, from a successful servers puts the service in error state
despite all remaining components in successfully "Deployed" state.
Resolution/Workaround : Retry the service should move the service state
back to successful.
• Issue: ASM-4174: ASM backend not to tear down the shared resources.
Description : When deleting a service the user has the option to delete
clusters and storage. If these are shared with other services, ASM will not
warn the user and will proceed to remove the shared resources.
Resolution/Workaround : Prior to deleting a service, verify which clusters and
storage volumes are shared with other services. Only select delete for
resources which will not impact other services.
• Issue: ASM-4205 : ESXi 6.0 with Compellent will fail if the array has firmware version later
than v6.6.
Description : vCenter 6.0 support is added with Storage Center 6.6. While
creating a deployment with ESXi 6.0, select Compellent for which storage
center is upgraded to version 6.6
Resolution/Workaround : In case the storage center is running on version less
than 6.6, then for Compellent Storage Component, select Operating System
as "ESXi 5.5" or "ESXi 5.1"
• Issue: ASM-4273 : Volumes deleted from a HyperV service in ASM are not removed
completely from the HyperV host.
Description : If you delete a storage volume from a HyperV service, the
volume will be deleted on the storage array and removed from ASM service,
but there may be stale references left on HyperV hosts.
Resolution/Workaround : Manually remove references to non-existent
volumes in HyperV using disk manager.
• Issue: ASM-4328 : After restore, operating system and firmware need to be able to be
rebuilt.
Description : After a restore, operating system and firmware repositories are
placeholders. The user must now remove the repositories and add new ones.
However, any existing templates or services that rely on the repositories will
prevent the existing repositories from being deleted in order to be re-added.
Hence, the user has to change the repositories for all templates, and any
existing services will have to be deleted in order to point to the correct
repository.
Resolution/Workaround : For any repositories, they cannot be used for new
templates or as an option for adding resources to a service, and provide a
method to rebuild the existing repository without requiring deletion.
• Issue: ASM-4561: Problem with 7.12 Broadcom firmware.
Description : Broadcom NIC firmware 7.12.xx is not compatible with ASM. It
can cause intermittent connectivity issues which will result in hypervisor and
bare metal OS deployment failures.
o
Resolution/Workaround : Apply the firmware available in the latest ASM
catalog. Alternatively, manually downgrade your Broadcom NIC firmware to