Updated on: 23 Oct 2019
vRealize Suite Lifecycle Manager 8.0 | 17 Oct 2019 | Build 14878991
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- About vRealize Suite Lifecycle Manager 8.0
- What's New in vRealize Suite Lifecycle Manager 8.0
- Resolved Issues
- Known Issues
- vRealize Suite Lifecycle Manager Support for VMware Identity Manager Connector
About vRealize Suite Lifecycle Manager 8.0
VMware vRealize™ Suite 2019 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.
The vRealize Suite Lifecycle Manager automates installation, configuration, upgrade, patch, configuration management, and health from within a single pane of glass. This provides the IT Managers or Cloud admin resources to focus on business-critical initiatives, while improving time to value (TTV), reliability and consistency.
You can migrate from vRealize Suite Lifecycle Manager 1.3 version and later to vRealize Suite Lifecycle Manager 8.0. To know more, click here.
Install VMware vRealize Suite Lifecycle Manager 8.0 first to simplify your deployment and on-going management of the vRealize products.
What's New in vRealize Suite Lifecycle Manager 8.0
- Easy Installer
A simple, intuitive, wizard based installer for installing vRealize Suite Lifecycle Manager 8.0, vRealize Automation 8.0 and VMware Identity Manager.
- Extended lifecycle management of Identity Manager (Workspace One Access)
- Cluster, Scale-out and Windows connector deployment for the latest version (3.3.1) of VMware Identity Manager.
- Full-fledged directory management available from User Management app allowing users to add 3 different flavors (AD over LDAP, AD with IWA, LDAPS) of active directory to VMware Identity Manager through vRealize Suite Lifecycle Manager.
- Enhanced user experience
- New services based layout which provides better navigation and grouping. Intuitive navigation and better troubleshooting guidance.
- Inventory sync to synchronize changes done outside of vRealize Suite Lifecycle Manager.
- Improved support for License, certificate and password management
New dedicated service called Locker for managing licenses, certificates and passwords for vRealize Suite of products.
- Improved content management capabilities
- Ability to work with multiple branches (capture from one scm/branch and check-in to another scm/branch)
- Multi-delete (versions/contents) and multi-test
- Public API support for content operations
- Improvements on pipeline stub configuration
- Multiple check-ins --> generate combined merge requests based on commit hash references
- Migration from earlier versions of vRealize Suite Lifecycle Manager to the 8.0 version
- Migration of environments, configurations, and content endpoints.
vRealize Suite Lifecycle Manager Support for VMware Identity Manager Connector
Announcing the general availability of vRealize Suite Lifecycle Manager Product Support Pack.
Note: This is a support pack that enables vRealize Identity Manager windows connector deployment.
Update the vRealize Suite Lifecycle Manager windows connector support when vRealize Lifecycle Manager is connected to the internet:
- Access Lifecycle Manager UI and navigate to Lifecycle Operations > Settings > Update.
- Scroll down to Support for Additional Product Versions section. The vRealize Suite Lifecycle Manager auto-populates the list of available support versions. If the list is not auto-populated, click Check for Versions.
- When the list is populated, click Apply Version for the appropriate content version.
- After applying the version, download the windows connector binary from My VMware by downloading the VMware Identity Manager 3.3.1 Upgrade binary from the list.
Note: Update version in the policy points to VMware Identity Manager 3.3.1.
Update the vRealize Suite Lifecycle Manager windows connector support when vRealize Lifecycle Manager is not connected to the internet:
- Download the product support pack file from the VMware Market place.
- From the vRealize Lifecycle Manager UI, navigate to Lifecycle Operations > Settings > Update.
- Scroll down to Support for Additional Product Versions section.
- To upload the downloaded product support pack file, click Choose File. The vRealize Suite Lifecycle Manager auto-populates the list of available support versions.
- When the list is populated, click Apply Version for the appropriate content version.
- Navigate to Binary Mapping and map the connector .zip and install windows connector.
Note: Update version in the policy points to VMware Identity Manager 3.3.1.
After you have added the .pspak file successfully, refresh the UI. Click here to download the product support pack.
- Content Migration from 1.3, 2.0 and 2.1 is not supported in vRealize Suite Lifecycle Manager 8.0. For more information, see Content Management.
- Support of content from an earlier version to the latest depends on the product capabilities.
You can capture content from vRealize Automation.5 and release to vRealize Automation 7.6. However, if vRealize Automation 7.6 does not support contents captured from older version, it would not work in Lifecycle Manager as well.
- Multimode deployment of ISO and Template for an IaaS deployment is not supported.
In a single deployment of vRealize Automation, you can deploy IaaS VMs using a template or ISO. A combination of both is not supported.
- ISO image mapping that is specific to a locale or a user-specified operating system distribution is not supported from Lifecycle Manager
- vRO package name cannot contain special characters and the package is not validated
A vRO package name cannot contain special characters and can cause issues when you capture, release or check-in a content. If you have a vRO package name with a space in between the name, then the space is converted to an underscore (_) during a capture and fails during a test and deploy.
- If the environment name contains a space then GET drift report which uses API does not appear
If the environment name contains a space then GET drift report which uses API does not appear.
- Scale-out of a vRealize Automation 7.x small environment is not supported in the vRealize Suite Lifecycle Manager
To scale out vRealize Automation small HA, medium HA or a large environment, you can add the components by clicking Add Node in the product cards on the Manage Environment page.
- 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, such product VMs will not be managed by vRealize Suite Lifecycle Manager.
- vRealize Orchestrator package can scale up to 1000 elements in a package.
vRealize Orchestrator package can scale up to 1000 elements in a package.
- Snapshot for VMs remain in the "In progress" state in vRealize Suite Lifecycle Manager
Snapshot for VMs that have device back up are not supported and remain in the "In-progress" state in vRealize Suite Lifecycle Manager. You cannot take a snapshot of VMs that have a device back up in vCenter. vRealize Suite Lifecycle Manager also supports taking snapshots of VMs. However, the vCenter server also supports taking device back up. For such VMs, vRealize Suite Lifecycle Manager snapshot requests would remain In Progress.
- Test and deployment of a content is getting failed in an Azure machine
vRealize Suite Lifecycle Manager does not support an Azure machine in content management for testing and releasing content.
- vRealize Operations upgrade failed at application upgrade task after completing the OS upgrade task and the cluster does not come online
When Cassandra fails in one of the vRealize Operations nodes, this causes the vRealize Operations cluster to not come online.
- Test and deployment of XaaS blueprint "Azure Machine" shipped by default with vRealize Automation fails
XaaS blueprint "Azure Machine" is shipped by default with vRealize Automation. However, transfer of XaaS blueprint between vRealize Automation environments is not supported.
- vRealize Suite Lifecycle Manager Cloud Admin can view the Content Management tab but does not have access to the vRealize Suite Lifecycle Manager UI
vRealize Suite Lifecycle Manager UI is not accessible whereas the content management tab is visible for a cloud admin.
- Prolonged activity for 15 to 30 minutes only on the content pipelines page leads to session timeout for Lifecycle Manager.
Working continuously on Content pipelines page without clicking other tabs of Lifecycle Manager leads to Session Timeout.
- Installation of Content fails on a newly created environment
The license of newly created environments cannot be listed until a marketplace sync is triggered.
- vRealize Business for Cloud upgrade may fail if the root passwords of vRealize Business for Cloud server and vRealize Business for Cloud Remote Collector are not same
When you upgrade vRealize Business for Cloud using Lifecycle Manager UI, the server and the remote collector should have same root passwords. If the passwords are different then upgrade may fail and you are asked to enter the correct password in the retry.
- 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 the vRealize Suite Lifecycle Manager, delete environment operations and snapshots in the environment fail.
- You can see multiple catalog app tiles and application links of vRealize Suite Lifecycle Manager after you register with VMware Identity Manager
After you register with VMware Identity Manager in vRealize Suite Lifecycle Manager, and you click Update from the Settings > User Management tab multiple times, an equal number of catalog application tiles and application links of vRealize Suite Lifecycle Manager are created.
- Some services does not start after rebooting the vRealize Suite Lifecycle Manager appliance.
Some services does not start even after rebooting the vRSLCM virtual appliance, as there could be some unwanted internal ports available outside after rebooting the vRealize Suite Lifecycle Manager Virtual appliance.
After deploying the vRealize Suite Lifecycle Manager Virtual appliance from the easy installer, login to vRealize Suite Lifecycle Manager Virtual appliance through SSH and run command.
rm -rf /etc/bootstrap/everyboot.d/10-start-services
- [New] vRealize Suite Lifecycle Manager does not support changed Primary Network Identifiers for vCenter Server.
vSphere 6.5 U3 and 6.7 U3 supports updating Primary Network Identifiers (PNID) without any downtime. But vRealize Suite Lifecycle Manager 2.1 does not support this for the specified versions.
If PNID is changed for a vCenter server that is already registered in Lifecycle Manager with Lifecycle Manager managed products present in the vCenter server, then Lifecycle Manager loses communication with that vCenter Server. As a result, all operations on the Lifecycle Manager managed products deployed on vCenter are likely to fail.
Workaround: After changing the PNID:
- Verify if the vCenter server is still reachable from vRealize Suite Lifecycle Manager.
- If the vCenter Server is reachable after the PNID update, re-register the vCenter Server in vRealize Suite Lifecycle Manager.
- Once vCenter Server data collection succeeds then import the managed products from the vCenter server in Lifecycle Manager. Once the import is complete, Lifecycle Manager monitors the products.
- [New]: The time settings page is not enabled to make changes when you provide NTP details after deploying vRealize Suite Lifecycle Manager.
On a usual scenario, when you provide the NTP details at the time of vRealize Suite Lifecycle Manager deployment, the same is reflected on the time settings page. You cannot make changes to the existing NTP details as the Select button on the UI is disabled. However, you can still select Use Host Time or Add New NTP details.
- Navigate to Lifecycle Operations ->Settings -> Time Settings.
- Add at-least one NTP server in vRealize Suite Lifecycle Manager UI.
Once a new NTP server is added, the 'SELECT' button will get enabled and user can make the changes in NTP server for system using SELECT button.
- [New] Content management functionality does not work after replacing the Lifecycle Manager certificate
This issue occurs:
- When you provide the certificate details during an OVA deployment.
- When you change the SSH password twice and admin password once directly from UI.
- The test connection fails with an invalid credential for source control endpoints only.
- Bitbucket, GitLab, and vSphere displays invalid credentials.
Open SSH in Lifecycle Manager, and run the following command:
systemctl restart blackstone-spring
- vRealize Automation precheck fails while checking the VMware tools version
vRealize Automation Precheck on SUBMIT fails while checking the guest tools version and there is no resume option on the create environment wizard to re-run the precheck.
- Update the VMware tool version 10.1.0 and trigger the create environment.
- Click Precheck.
- Content Management operations fail on vRealize Automation end-point after updating the certificate.
The certificate can be updated on the vRealize Automation appliance through Lifecycle Manageror by using the vRealize Automation product VAMI interface. This causes content management operations to fail on vRealize Automation end-point.
Once a certificate is replaced by Lifecycle Manager, a restart of the embedded vRealize Orchestrator is required on the LCM appliance for the Test Connection and all other content operations to continue to work. Note that this is required for vRealize Automation endpoint only.
SSH to the LCM Appliance as user root and run the command:
"systemctl restart vco-server"
- Users other than local VMware Identity Manager admin users cannot be used for VMware Identity Manager registration in vRealize Suite Lifecycle Manager
When registering an external VMware Identity Manager into vRealize Suite Lifecycle Manager, the credentials of users other than local VMware Identity Manager admin users does not lead to a successful registration.
Workaround: Use local VMware Identity Manager admin user credentials for registration of VMware Identity Manager to vRealize Suite Lifecycle Manager.
- vRealize Automation upgrade fails at vRealize Automation Services Restart step with an error message
If some of the vRealize Automation services are not started post the vRealize Automation virtual appliance upgrade within 45 minutes then the following error message appears:
Services on this VA failed to start within 45 minutes. IaaS upgrade will not proceed.
- Reboot the vRealize Automation cafe VMs.
- Make sure all the vRealize Automation services are running.
- Retry the failed upgrade request from vRealize Lifecycle Manager Requests page.
- The retry inputs provided in the failed deployment request is not saved.
The retry inputs provided in the failed deployment request is not getting saved and the next task in the deployment request fails again with the old input provided during the deployment.
Workaround: Provide the retry inputs for each failed task in the deployment request or you should to re-deploy the environment with correct inputs.
- Pre-Check succeeds but actual deployment fails due to insufficient disk space
Pre-Check in LCM does not take extended storage into account. This means if the extended storage option is used to deploy vRealize Operation nodes using vRSLCM, then the precheck might succeed but the actual deployment can still fail due to insufficient disk space.
To avoid deployment failure, analyze the available disk space and select appropriate data store before opting to deploy vRealize Operation from vRealize Suite Life Cycle Manager. If thin disk format is provided then user needs to make sure that sufficient disk space is available for the appliance to install. If extended storage option is opted for certain vRealize Operation nodes, then 1 TB extra storage space is required for each those nodes.
vRealize Automation 8.0 HA Initialize cluster fails when vRealize Automation Load Balancer configuration is wrong
Workaround: Verfiy if the vRealize Automation Load Balancer has been configured correctly and trigger the vRealize Automation HA deployment again.
vRealize Automation 8.0 initialize cluster fails when SSL pass through is not enabled in NSX Load Balancer for vRealize Automation
Workaround: Enable the SSL passthrough the vRealize Automation Load balancer before you trigger the vRealize Automation 8.0 HA deployment.