times

vRealize Suite Lifecycle Manager 8.6 | 12 October 2021 | Build 18747913

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New
Recommendations
Limitations
Security Updates for Multiple Vulnerabilities
Resolved Issues
Known Issues

What's New

Here are the key features and capabilities of vRealize Suite Lifecycle Manager 8.6:

Cloud Proxy deployment

VCF enhancements

Snapshot management enhancements

Outbound notification integration

vRealize Operations Manager support improvements

Technical debt and product improvements

Marketplace improvements
- Previously, Marketplace connected with VMware Solutions Exchange to download content in vRealize Suite Lifecycle Manager. VMware Solutions Exchange is now deprecated, so Marketplace fetches the required content from VMware Cloud Marketplace.

Content Management enhancements
- The version history is now captured for Orchestrator Action and Orchestrator-ConfigurationElement when capturing the Orchestrator workflow.
- You can deploy or publish cloud templates and XaaSBlueprints when releasing these content types.

vRealize Cloud Universal simplification to help our users

Perpetual and vRealize Cloud Universal licenses in vRealize Suite Lifecycle Manager

Note: You can now provide customer feedback directly to the engineering and product development teams to address product improvement opportunities.

If the source vRealize Automation has 8.0.0 GA or 8.0.1 GA, ensure that KB 78235 is applied before upgrading to restore expired root accounts.
When configuring multi-tenancy in vRealize Suite Lifecycle Manager for VMware Identity Manager and vRealize Automation, if you replace VMware Identity Manager certificate, it can cause service downtime on products integrated with VMware Identity Manager. Hence, it is suggested to create SAN certificates with required hostnames for multi-tenancy. To avoid service disruption, use wildcard certificates on VMware Identity Manager.
To reboot VMware Identity Manager cluster setup, use the Power On and Power Off options in the VMware Identity Manager product actions in vRealize Suite Lifecycle Manager.

Limitations

vRealize Suite Lifecycle Manager cannot be upgraded using VMware Remote console in Windows VM: During an vRealize Suite Lifecycle Manager upgrade, the ISO filename is truncated after it is mounted in Windows VM. For an upgrade, ensure that you upload the ISO filename in a content library of the vCenter server or upload it to a datastore that the vRealize Suite Lifecycle Manager VM can access. After uploading the ISO filename, attach the ISO to the CD-ROM device of the vRealize Suite Lifecycle Manager VM by editing the hardware configuration from the vCenter inventory of the VM. From the vRealize Suite Lifecycle Manager UI, select CD-ROM based upgrade option, and then click proceed.

vRealize Automation SaltStack Config cannot be downloaded from My VMware in the vRealize Suite Lifecycle Manager Settings> Binary Mapping> Product Binaries page as the vRealize Automation SaltStack Config product binary is not available in the vRealize Suite download page. For more details and the workaround, refer to KB 82543.

If a custom form is released without a blueprint at the target vRealize Automation, even if the release is successful on vRealize Suite Lifecycle Manager, the custom form is not visible at the target vRealize Automation instance. To release a custom form, ensure that the associated composite blueprint is released or created first on the target vRealize Automation.

Content source on vRealize Automation 8.x endpoint: When releasing a blueprint on vRealize Automation 8.x, you must create the content source on the target vRealize Automation 8.x prior to the release.

vRealize Automation 8.x content types: The vRealize Automation 8.x content types which are renamed must be re-captured from the vRealize Automation endpoints, and then checked in to the source control endpoints. If the content is present in the source control, then you must manually rename the folder in the source control endpoints, and then check-out the content from the source control endpoints.

Content Migration from 1.3, 2.0 and 2.1 are not supported in vRealize Suite Lifecycle Manager 8.0.1 and later. For more information, see Content Management.

Support of content from an earlier version to the latest version depends on the product capabilities: You can capture content from vRealize Automation 7.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 vRealize Suite Lifecycle Manager.

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 snapshots 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.

vRealize Operations upgrade failed at application upgrade task after completing the OS upgrade task and the cluster is not online:
When Cassandra fails in one of the vRealize Operations nodes, this causes the vRealize Operations cluster to be offline.

Security Updates for Multiple Vulnerabilities

vRealize Suite Lifecycle Manager 8.6 has the following CVEs addressed.

Photon OS Components	Fixed Versions	CVEs Addressed
gnutls	gnutls-3.6.15-3	CVE-2021-20232
nginx	nginx-1.16.1-4	CVE-2021-23017
libxml2, libxml2-devel, libxml2-python	libxml2-2.9.11-2, libxml2-devel-2.9.11-2, libxml2-python-2.9.11-2	CVE-2021-3517, CVE-2021-3518, CVE-2021-3537
glibc, glibc-i18n, glibc-iconv, glibc-lang	glibc-2.28-15, glibc-i18n-2.28-15, glibc-iconv-2.28-15, glibc-lang-2.28-15	CVE-2021-35942, CVE-2021-33574
linux	linux-4.19.198-2	CVE-2021-33909
python-cryptography	python-cryptography-2.8-2	CVE-2020-36242
nss, nss-libs	nss-3.44-6, nss-libs-3.44-6	CVE-2020-12403
bindutils	bindutils-9.16.15-1	CVE-2021-25214, CVE-2021-25215, CVE-2021-25216
curl, curl-libs	curl-7.78.0-2, curl-libs-7.78.0-2	CVE-2021-22945, CVE-2021-22946, CVE-2021-22947

Resolved Issues

VCF Enabled Password Error After Upgrading vRealize Suite Lifecycle Manager
When you upgrade from vRealize Suite Lifecycle Manager version 8.2.1 to a later version but prior to version 8.6, and then perform an inventory sync of the environment, you may not be able to edit passwords from Locker. You may receive the following error message:
```
The Password edit is not allowed for VCF enabled environment
```
Workaround: If you upgrade from vRealize Suite Lifecycle Manager version 8.2.1 to a later version but prior to version 8.6.0, ensure that you reimport the environments of the vRealize Suite Lifecycle Manager inventory.
vRealize Suite Lifecycle Manager user interface not accessible post upgrade
When upgrading vRealize Suite Lifecycle Manager, if VMware Identity Manager API does not respond, the upgrade fails with the following error:
```
SYSOUT/SYSERR CAPTURED:  -- org.springframework.web.client.
ResourceAccessException: I/O error on GET request for "https://[vIDM hostname]/SAAS/API/1.0/REST/auth/token":
Connection reset; nested exception is java.net.SocketException: Connection reset”.
This can be verified by looking at logs available under /var/log/vmware_vrlcm.log.
```
Workaround:
1. Revert snapshot.
2. Ensure that VMware Identity Manager responds through vRealize Suite Lifecycle Manager and the VMware Identity Manager inventory sync is successful, prior to an upgrade.

Known Issues