Release Notes

be deployed until you manually re-create repositories.
Description: After you restore a backup to an ASM virtual appliance, the backup cannot re-create OS
installation repositories. The service cannot be deployed using non ESXi-OS after restore until you
re-create their OS repositories in Razor.
Resolution/Workaround: After performing a restore, make sure all OS install repositories are re-
created.
Issue [ASM-1291]: If the configure components are not selected in correct order in a template, the
information is not saved successfully.
Description: If you do not update the template components in the appropriate order then information
and settings that you enter in a template are not saved successfully.
Resolution/Workaround: Create a template starting with dependent items first. For example, when
you
create a template with storage, server, and cluster components, makes sure to create the storage
component, then the server component, and finally the cluster component.
Issue [ASM-1260]: An operator cannot delete an unsuccessful service deployment.
Description: An operator can initiate a service deployment, but ASM does not provide the ability for an
operator to delete that service. The Delete button is greyed out.
Resolution/Workaround: Only an admin user can delete a service that is failed.
Issue [ASM-1255]: Default template passwords are not displayed, and the users are not prompted to
change the password.
Description: Default templates that ship with ASM appear to contain passwords because a masked value
is visible in password fields. Actually a password is not present, so this causes issues during service
deployment.
Resolution/Workaround: Make sure that any default template is cloned, and then passwords are
updated for the new template.
Issue [ASM-1198]: Issue while provisioning virtual machines with hostname that has already been used.
Description: If you provide the same name of the virtual machine which exists for an earlier deployment
to vCenter, even if it does not exist anymore, virtual machines cannot be provisioned. The virtual
machine is created on vCenter, but the OS cannot be installed on the virtual machine and virtual
machines are not provisioned indicating an error.
Resolution/Workaround: You cannot use the same virtual machine name on subsequent deployments.
Issue [ASM-1196]: The Windows unattend file contains a clear text password.
Description: The Windows unattend.xml.erb file contains a clear text password. This password is
required for razor to install Windows. It is accessible through the svc URL, which should be isolated on
the PXE network.
Resolution/Workaround: You should make sure that the password is changed after the Windows install