Release Notes

Description : ASM includes a puppet agent while installing the Windows or
Linux operating systems. The puppet agent communicates with the ASM
appliance to retrieve the post-install configuration and both server (ASM) and
client-side SSL certificates are checked for validity during this process. The
ASM server-side SSL certificate is created when the ASM appliance is first
started and is marked valid only after the first boot time of the appliance.
Hence, a failure may occur if the initial time set on the appliance is incorrect.
To view this issue, manually run the "puppet agent -t" command on the server
or VM that is experiencing a failure. This problem usually results in
SSL_connect errors in the output and the following message is displayed:
CRL
is not yet valid for /CN=dellasm
.
Resolution/Workaround :
Ensure that the hypervisor host on which you want to install ASM is set to the
correct time and NTP is used for the ASM appliance, ASM installed servers,
virtual machines to ensure consistency in the time.
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-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.