What's in the Release Notes

The release notes cover the following topics:

About vRealize Suite Lifecycle Manager 1.1
What's New in vRealize Suite Lifecycle Manager 1.1
Resolved Issues
Known Issues

About vRealize Suite Lifecycle Manager 1.1

VMware vRealize™ Suite 2012 is the complete cloud management solution, delivering and managing infrastructure and applications quickly while maintaining IT control. It provides a comprehensive management stack for IT services on vSphere and other hypervisors, physical infrastructure, and multiple public clouds.

Install VMware vRealize Suite Lifecycle Manager 1.1 first to simplify your deployment and on-going management of the vRealize products.

What's New in vRealize Suite Lifecycle Manager 1.1

In-product Marketplace that allows you to browse and install VMware Marketplace content for all the vRealize products. It not only filters the content as for the available environments and product versions, but also notifies you of any updates to installed Marketplace content.
Configuration drift remediation enhances the existing ability to view the configuration drift for an environment with remediation against good state capabilities.
Support for delete environment allows you to delete an environment managed by vRealize Suite Lifecycle Manager. You can optionally choose to delete the product deployments in the environment.
Error handling and validation enhancements to environment installations, upgrades, and retry logic.

Resolved Issues

vRealize Suite Lifecycle Manager does not work on Microsoft Internet Explorer 11
vRealize Suite Lifecycle Manager does not support Microsoft Internet Explorer 11 in this release.

Workaround: Choose a different browser to access vRealize Suite Lifecycle Manager.
When you add a replica node to an existing vRealize Operations Manager environment, the replica node does not join the vRealize Operations Manager cluster and the node addition/scale-out operation fails in vRealize Suite Lifecycle Manager
When you do a scale out/component addition to an existing vRealize Operations Manager, replica node addition fails. The replica VM is deployed, but when it tries to join the vRealize Operations Manager cluster, it fails. Consider a situation where the vRealize Operations Manager setup has a master node. You can add three types of nodes at this time: data node, replica node, and remote collector. Adding a data node or remote collector works fine, but adding a replica node fails.

Workaround: Use the vRealize Operations Manager user interface to add the replica node.
When the baseline configuration is created for vRealize Business for Cloud, Azure endpoints that have been configured are not collected and analyzed for configuration changes
In cases where you add an Azure public cloud endpoint the vRealize Business for Cloud after you have created a product baseline for that instance of vRealize Business for Cloud in vRealize Suite Lifecycle Manager, configuration drift reports in vRealize Suite Lifecycle Manager do not capture configurations for the Azure endpoint.

Workaround: None.
When you register to My VMware from the VMware vRealize Suite Lifecycle Manager Settings page, downloading the product OVA does not work
This problem happens after you download and deploy the vRealize Suite Lifecycle Manager virtual appliance. If in your organization the vRealize Suite Lifecycle Manager deployment requires a proxy to access the My VMware (my.vmware.com) portal, you must configure the proxy in Settings > Proxy to download the product binaries from My VMware.
vIDM deployment using vRealize Suite Life Cycle Manager fails when vIDM is downloaded from My VMware using vRealize Suite Lifecycle Manager
When you deploy vIDM using vRealize Suite Lifecycle Manager after downloading vIDM from My VMware using vRealize Suite Lifecycle Manager, the deployment fails with the error message Invalid network in property netmask0.

After vIDM OVAs downloaded from My VMware using vRSLCM, verify the Product Binary name of VMware Identity Manager present at vRealize Suite Lifecycle Manager's Settings page > OVA Configuration tab > Source Location option. If the product binary name contains euc-unified-access-gateway or identity-manager-connector, then that is a wrong mapping.

Workaround: Correct the OVA source file mapping of vIDM.
1. Browse to OVA configuration tab under the Settings tab.
2. Delete the VMware Identity Manager OVA source entry using delete icon.
3. Select My VMware from Source Location Type dropdown.
4. Select VMware Identity Manager from Product Name dropdown.
5. Select the required vIDM version from Product Version dropdown.
6. Select Install from Product Binary Type dropdown.
7. In the Product Binary dropdown select a ova file name that does not contain euc-unified-access-gateway or identity-manager-connector.
  For example: correct OVA source file name of vIDM : identity-manager-2.9.2.0-6095217_OVF10.ova
8. Click on Save button, this will create a new OVA source file mapping for vIDM installation.

Known Issues

Users other than local vIDM admin users can not be used for vIDM registration in vRealize Suite Lifecycle Manager
When registering an external vIDM into vRealize Suite Lifecycle Manager, the credentials of users other than local vIDM admin users does not lead to a successful registration.

Workaround: Use local vIDM admin user credentials for registration of vIDM to vRealize Suite Lifecycle Manager.
In vCenter, if a duplicate cluster is found inside a data center, only the first cluster is listed in the vRealize Suite Lifecycle Manager install wizard
In vCenter, if a duplicate cluster is found inside a data center, after vCenter data collection completes, only the first cluster appears in the wizard.

Workaround: None
After upgrading vRealize Suite Lifecycle Manager from version 1.0 to version 1.1, the Configuration Drift interval is reset to 24 hours
When you upgrade vRealize Suite Lifecycle Manager to version 1.1, the Configuration Drift interval is reset to the default value of 24 hours. If you previously set a different Configuration Drift interval, that interval is overwritten.

Workaround: After you upgrade vRealize Suite Lifecycle Manager to version 1.1, go the the vRealize Suite Lifecycle Manager Settings page to change the Configuration Drift interval to the desired interval.
vRealize Operations Manager UI access from vIDM app catalog displays a 404 error
When you access vRealize Operations Manager from vIDM vApp Catalog for the second time after closing the vRealize Operations Manager tab opened for the first time, then vRealize Operations Manager UI displays a 404 error.

Workaround: Clear your browser cache and try again.
vRealize Business remote collector component is not listed in the vRealize Business product details page
When the vRealzie Business server that has vRealize Business remote collector components imported to vRealize Suite Lifecycle Manager, the vRealize Business remote collector components are not listed on the vRealize Business product details page.

Workaround: None.
The command to manage vRealize Suite Lifecycle Manager services has been modified
The commands to manage vRealize Suite Lifecycle Manager has been change in this release, and previous service commands do not work.

Workaround: Use the new service commands: systemctl {start|stop|restart} vlcm-server and systemctl {start|stop|restart} vlcm-xserver.
Product component details such as CPU, memory, power status, and version do not display under the product details page in Manage Private Cloud
When the suite product components are spread across two vCenters, and if you have not specified both vCenters as part of the import brownfield for the product, then component details that belong to the vCenter that is not provided aren't visible in the product details page.

Workaround: Provide both vCenters at product level during the import brownfield environment process even though one of the vCenters is provided in infrastructure level inputs.
Business Management tab not visible in vRealize Automation UI after suite deployment
If VMware Identity Manager is registered with vRealize Suite Lifecycle Manager, vRealize Business for Cloud might not have registered to vRealize Automation after successful deployement of the suite, causing the Business Management tab to not appear in the vRealize Automation UI.

Workaround: During vRealize Suite deployment, specify masterVidmEnabled property set to False in vRealize Buisness for Cloud server component in advanced properties of the suite install wizard.
vRealize Log Insight self-signed SSL certificate is not replaced by a vRealize Suite Lifecycle Manager custom certificate
By default, vRealize Log Insight installs a self-signed SSL certificate on the virtual appliance. vRealize Suite Lifecycle Manager generates custom certificates for products during environment creation, but custom certificate generation fails for vRealize Log Insight. The default vRealize Log Insight self-signed certificate generates security warnings when you connect to the vRealize Log Insight web user interface. If you enabled Integrated Load Balancer, you must generate a new certificate using the ILB IP as common name and replace the certificatesor the vRealize Log Insight Agents configured to connect to the Log Insight server through SSL rejects the connection.

Workaround: Generate or get a custom CA signed certificate. The generated certificate can be a wildcard, SAN, or ILB IP certificate. Upload the generated certificate to vRealize Log Insight from the SSL configuration menu on the Administration tab.
VMware Identity Manager authentication to vRealize Automation fails
Authentication to vRealize Automation via external VMware Identity Manager, either by clicking on the vRealize Automation application icon in the VMware Identity Manager catalog or manually logging in to vRealize Automation via the tenant URL, fails with the following error:Identity Manager encountered an error. Contact your admin and provide information displayed below.

Workaround: Ask your administrator to check the time on the VMware Identiy Manager and vRealize Automation virtual appliance to verify that they are properly synchronized.
Configuration drift fails when vRealize Automation primary and secondary virtual appliance nodes have different root passwords or the vRealize Operations Manager master node has a different root password than other nodes
When an existing vRealize Suite is imported into vRealize Suite Lifecycle Manager and the primary and secondary virtual appliance root passwords differ, virtual machine-related configurations like certificates, network details, and file based configurations are not collected from all virtual appliances as part of the baseline creation. Only the master or primary node virtual machine configurations will be collected during baseline creation.

Workaround: None.
vRealize Business for Cloud integration with vRealize Automation works only when vRealize Automation is added to a private cloud environment before vRealize Business for Cloud
Fresh deployment of vRealize Business for Cloud integration with vRealize Automation works only when vRealize Automation is added to a private cloud environment before vRealize Business for Cloud

Workaround: To integrate vRealize Buisness for Cloud with vRealize Automation, add vRealize Automation to the private cloud environment before or at the same time you add vRealize Business for Cloud.
Add Products and Scale Out actions fail when you configure the certificate for a product
When you use the Add Products or Scale Out actions to modify an environment, the product can fail if the new product host names or the components are not present in the SAN certificate provided when you create the environment for the first time.

Workaround: Generate a single SAN certificate with all the product or management virtual host names or a wild card certificate and provide this certificate when you create the environment for the first time. This ensures support for post provisioning actions such as Add Products and Scale Out.
vROPS cluster is not accessible after revert the snapshot of vROPS taken by LCM
vROPS setup is not accessible after revert the snapshot of vROPS as the vROPS cluster in inconsistent state.

Workaround:User should bring down the vROPS cluster offline before taking the snapshot of the vROPS VM. The steps are as follows,
1. Login to vROPS Admin UI and bring down the vROPS cluster offline.
2. Take the snapshot of the vROPS using LCM via Manage Environment page.
3. Login to vROPS Admin UI and bring up the vROPS cluster online.
Product deployment is triggered again after a deployment failure after vCenter Server rejects the operation or a user cancels the deployment in vCenter Server
vRealize Suite Lifecycle Manager retries product virtual machine deployment in the case of failures due to vCenter Server rejecting the operation or a user manually cancelling the deployment from vCenter Server.

Workaround: If the deployment is successful in vCenter Server, but fails during the virtual machine reachable check, manually delete the failed virtual machine in vCenter Server and retry the operation from Requests tab in vRealize Suite Lifecycle Manager.
Delete environment or snapshot fails when vCenter credentials are changed after the environment is deployed
When you change vCenter credentials after an environment is imported or deployed successfully in vRealize Suite Lifecycle Manager, delete environment operations and snapshots in the environment fail.

Workaround : None.
Link to download the vRealize Suite product support bundle is missing from the vRealize Suite Lifecycle Manager Manage Environments page
When you click download logs on the Manage Environments page in vRealize Suite Lifecycle Manager, the link to download the support bundle does not appear.

Workaround: After you click download logs on the Manage Environments page, download the vRealize Suite Product support bundle in the vRealize Suite Lifecycle Manager virtual appliace.
1. Use SSH to log in to the vRealize Suite Lifecycle Manager virtual appliance with root credentials.
2. Navigate to /data/support-bundle/ and download the support bundle.
NEW After vIDM configuration in vRealize Suite Lifecycle Manager, the vIDM server does not sync users who don't have email address in the user account
After the successful integration of vRealize Suite Lifecycle Manager with vIDM, users who don't have the email address in the active directory are not synced in the vIDM server.

Workaround: The vIDM server is configured with default mandatory attributes to be present for active directory users. They are userName, email, firstName, and lastName. To resolve the user sync issue, the vIDM admin must remove the email attribute from the user attributes list.
1. Log in to vIDM as the system domain admin user.
2. Click the Identity & Access Management tab.
3. Click Setup.
4. Click the User Attributes tab.
5. Deselect email in the Required column.
6. Click Manage.
7. Click Sync Now for the the active directory, and click Sync Directory.
8. Wait for the affected users to sync in vIDM.
NEW Full /data disk causes log bundle downloads, OVA mappings, and product deployments to fail
All data in the vRealize Suite Lifecycle Manager virtual appliance, such as product binaries and product support log bundles, are stored in the /data folder. The default size of the /data folder is 100 GB. When the size of /data reaches 100 GB, log bundle downloads, OVA mappings, product deployments fail.

Workaround: Increase the size of /data in the vRealize Suite Lifecycle Manager virtual appliance.
1. Power off the vRealize Site Lifecycle Manager virtual appliance in vCenter Server.
2. Edit the vRealize Suite Lifecycle Manager virtual appliance in vCenter to increase the size of the second disk from 100 GB to a higher value.
3. Power on the vRealize Suite Lifecycle Manager virtual appliance.
4. Log in to the vRealize Suite Lifecycle Manager virtual appliance.
5. Run the command df -h to verify that the disk size of /data is increased to the value you specified.
NEW vRealize Log Insight master and worker nodes are always deployed with a large size
For vRealize Log Insight deployments, the default node size is large. Even if you configure the deploy option as small or medium in the advanced properties of the vRealize Log Insight master or worker node, the node is deployed with a large node size.

Workaround: None.
NEW Remediation does not modify the property Configure ESXi Hosts in vRealize Log Insight vSphere integration
When you trigger remediation in vRealize Suite Lifecycle Manager, the process does not modify the vRealize Log Insight vSphere integration property Configure ESXi Hosts.

Workaround: Modify the property Configure ESXi Hosts in vRealize Suite Lifecycle Manager vSphere integration endpoint configuration.
NEW Create Environment using a configuration file fails due to incorrect password
If you are creating an environment by using a configuration file, and if the encoded flag is set to false and some of the passwords are in encrypted format or plain text, the deployment might fail due to an incorrect password.

Workaround: Either all passwords should be encrypted and the encoded flag should be set to true, or all of the passwords should be in plain text and the encoded flag should be set to false.
NEW If the upgrade of vRealize Suite Lifecycle Manager from 1.0 to 1.1 fails, no error message appears and you must restore to the last known good state from a snapshot
If the upgrade fails, no indication appears in the UI. To ensure that you can recover from an upgrade failure, create a snapshot of the vRealize Suite Lifecycle Manager 1.0 working state before you upgrade.

Workaround: A UI that remains in Maintenance mode for a long time during the upgrade can indicate an upgrade failure. To confirm an upgrade failure, log in to the vRealize Suite Lifecycle Manager appliance as root using SSH. View these log files:
```
/opt/vmware/var/log/vami/updatecli.log

/var/log/bootstrap/postupdate.log
```
If a failure occurred, you need to restore the snapshot and retry the upgrade process.
NEW Products upgraded in vRealize Suite Lifecycle Manager 1.1 that are installed in vRealize Suite Lifecycle Manager 1.0 do not get the upgraded version in the View Details page
vRealize Suite Product versions are not updated in View Details page if the products are installed in 1.0 and upgraded in 1.1.

Workaround: None.
NEW First Web node task fails after installing vRealize Automation management agent
During the installation of vRealize Automation, the first Web node task might fail after the vRealize Automation management agent is installed. This is caused by either a database installation failure or a connection timeout.

Workaround:

1. Manually uninstall vCloud Automation Center from the IaaS Web machine. Do not uninstall the vRealize Automation management agent).

2. If the database (vcac) was created, you must delete it.

3. Retry the installation from the vRealize Suite Lifecycle Request page.
NEW Remediation is not available in vRealize Suite Lifecycle Manager 1.1 for drift reports that were generated using 1.0
When vRealize Suite Lifecycle Manager is upgraded from 1.0 to 1.1, remediation is not available for drift reports that were generated using 1.0.

Workaround: After you upgrade to 1.1, wait for the first set of drift reports to be generated. Remediation is available on the new reports.
NEW You can't perform snapshot/upgrade of imported environment when the VM imported has a host name instead of a FQDN host name.
The FDQN is required to uniquely identify the machine.

Workaround: Before you import an environment, make sure that the VM in vCenter displays the FQDN on the vCenter Summary page.
NEW Day 2 operations fail after you deploy or import an environment by using vRealize Suite Lifecycle Manager
After deploying the vRealize suite of products by using vRealize Suite Lifecycle Manager, if any of the VMs are migrated across a vCenter, those product's VMs will not be managed by vRealize Suite Lifecycle Manager.

Workaround: None.
NEW For the import of a brownfield environment, the delete environment confirmation dialog box does not show the VM list, and the environment card recent activity is not be deleted or grayed out for Organic growth the environment
For the import of a brownfield environment, if you fail to add a vCenter list, the delete environment confirmation dialog box does not show the VMs that are in that particular vCenter. The environment card from the recent activity home page is not deleted or grayed out for Organic growth environment.

Workaround: You must manually clean up the VMs.
NEW Creating a snapshot of a vRealize Suite product from vRealize Suite Lifecycle Manager might fail
Day 2 operations that depend on vCenter, such as creating a snapshot, might fail if the guest tools are not running or if the IP address/Hostname is not visible in vCenter.

Workaround: Make sure that the IP address and host name of the VMs are visible in vCenter.
NEW vRealize Lifecycle Manager does not provide options to retry requests that fail due to unsupported password phrases by an individual vRealize Suite product
If you attempt to update the password of a vRealize Suite product with an unsupported phrase, such as a dictionary word, the password update request is rejected and the corresponding vRealize Lifecycle Manager request fails without enough information for debug.

Workaround: Tasks that fail due to this issue cannot be debugged in the vRealize Lifecycle Manager UI. Check the logs to determine if this issue was caused by a password failure, check the 'catalina.out' in the vRealize Lifecycle Manager appliance log to understand the exceptions. An alternate workaround is to try the product password update outside of vRealize Lifecycle Manager and observe if the entered phrase is supported.
NEW During an upgrade from vRealize Suite Lifecycle Manager 1.0, an update check with a Default repository type displays the same build information as the previous Repository URL check
If an incorrect URL is used in the Repository URL field, all subsequent update attempts that use the Default option fail.

Workaround: To resolve this issue, try these workarounds:

- Retry the update and use a Repository URL with a supported link, and then check for updates by using the Default option.

- Log in to the vRealize Suite Lifecycle Manager appliance by using SSH and delete the file named – /opt/vmware/var/lib/vami/update/provider/provider-runtime.xml and retry the update check from the UI by using 'Default' option.
NEW For scale out of a vRealize Automation small environment, the option for providing load balancer input does not appear
Scale out of a vRealize Automation small environment is not supported in the vRealize Suite Life Cycle Manager.

Workaround: To scale out vRealize Automation smallha/mediumha/large environment, you can add the components from addNode in product cards on the Manage Environment page.
NEW vRealize Operations upgrade failed at application upgrade task after completing the OS upgrade task and the cluster does not come online
Cassandra failed in one of the vRealize Operations node and caused the vRealize Operations cluster to not come online.

Workaround: You need to revert the snapshot to the previous working state and retry the upgrade.
NEW Snapshot for VMs remain in the "in progress" state in vRealize Suite Lifecycle Manager.
Snapshot for VMs that have device backing are not supported and remain in the "in progress" state in vRealize Suite Lifecycle Manager.

Workaround: None. vCenter does not support the snapshot for VMs that have device backing.
NEW Admin logged into vRealize Operations has Read-Only Access
If VIDM is integrated with vRealize Suite Lifecycle Manager, when vRealize Operations is deployed from vRealize Suite Lifecycle Manager, administrative privilege are not assigned to the VIDM Admin.

Workaround: After vRealize Operations is successfully deployed from vRealize Suite Lifecycle Manager:

1. Log in to the vRealize Operations UI by accessing https:// /ui and by using the local Administratoraccount.The default user name is 'admin' and password is same as the default password provided in vRealize Suite Lifecycle Manager during the vRealize Operations deployment.

2. Navigate to Administration > Access Control.The necessary additional privileges might be granted to the VIDM Admin. For detailed information on setting up access control in vRealize Operations, see:
- vRealize Operations Manager 6.5.x documentation
- vRealize Operations Manager 6.6.x documentation