Here is the release date and build number for the VMware Aria Suite Lifecycle 8.12 release. Check for additions and updates to these release notes.
| Release |
Release Date |
Build Number |
| VMware Aria Suite Lifecycle 8.12 |
April 20, 2023 |
21628952 |
VMware is excited to announce that vRealize Suite Lifecycle Manager, VMware's powerful platform for lifecycle management, has been rebranded to VMware Aria Suite Lifecycle. This rebranding reflects our commitment to a comprehensive solution for deploying, configuring, managing, and upgrading the VMware Aria Suite of products.
With VMware Aria Suite Lifecycle, you can continue to rely on the same robust capabilities that vRealize Suite Lifecycle Manager provided. Additionally, you can expect even more advanced features and functionality as we continue to invest in the platform.
The rebranding does not impact your existing deployment of vRealize Suite Lifecycle Manager. You will continue to receive the same level of support and service that you have come to expect from VMware.
Note: All existing vRealize Products managed by vRealize Suite Lifecycle Manager will be referred using VMware Aria branding after an upgrade to VMware Aria Suite Lifecycle.
You cannot directly upgrade a VMware vRealize Suite Lifecycle Manager 2.x environment to VMware Aria Suite Lifecycle 8.12.0. To upgrade to version 8.12.0, first migrate your 2.x environment to VMware vRealize Suite Lifecycle Manager 8.8.x to 8.10 and then upgrade to VMware Aria Suite Lifecycle 8.12.0.
Here are the key features and capabilities of vRealize Suite Lifecycle Manager 8.12:
vRealize Suite products have been renamed with the VMware Aria family of products.
vRealize Suite Lifecycle Manager is now named VMware Aria Suite Lifecycle. Earlier product releases continue to use the vRealize Suite Lifecycle Manager name.
Power Off / On Day-2 actions for VMware Aria Operations for Networks (previously vRealize Network Insight) are now supported.
Installing and importing VMware Aria Automation Orchestrator (previously vRealize Orchestrator) with vSphere authentication is now supported.
Instances of offensive terminology have been removed from the VMware Aria Suite Lifecycle product and its documentation.
VMware Aria Suite Lifecycle is now empowered with Common Appliance Platform (CAP), which replaces the VMware Appliance Management Interface (VAMI) for product installations and upgrades.
VCF-awareness now provides the option to choose between an NSX Advanced Load Balancer and an NSX-T Load Balancer during product deployments.
The vRealize Suite license now supports VMware Aria Automation Config (previously vRealize SaltStack Config).
Significant reduction in time taken for VMware Aria Operations upgrade. Starting with version 8.12, the improve process includes the following steps: take the VMware Aria Operations cluster offline, take a snapshot , perform an upgrade then bring the cluster online as opposed to bringing the cluster online after snapshot and then shutting it down again to perform an upgrade.
vCenter inventory synchronization enhancements have been incorporated.
The new documentation landing page for VMware Aria Suite Lifecycle is https://docs.vmware.com/en/VMware-Aria-Suite-Lifecycle/index.html.
Support for vRealize Business has been discontinued.
VMware Aria Suite Lifecycle 8.12 supports VMware Cloud Foundation 5.0.
VMware Aria Operations for Networks installation fails
VMware Aria Operations for Networks installation fails during the "DeployOvf" task when being deployed on vCenter Server 8.0 U2.vCenter Server would display an error stating "A general system error occurred: PBM error occurred during PreCreateCheckCallback: Invalid state"
Workaround: Map the privilege "Storage Views --> View" and "VM storage policies" --> "View VM storage policies” to the service account being used to deploy
VMware Identity Manager Install binary download fails
The download of the VMware Identity Manager Install binary is failing because of a recent checksum change in the Windows connector included with the binary. Attempting to download it from Suite Lifecycle's product binary page will lead to a checksum exception
Workaround: To address this issue, manually download the VMware Identity Manager install binary from Customer Connect and then associate it with Suite Lifecycle.
VMware Aria Suite Lifecycle cannot be upgraded using the VMware Remote console in Windows VM.
During a VMware Aria Suite Lifecycle upgrade, the ISO filename is truncated after it is mounted in Windows VM.
Workaround: For an upgrade, upload the ISO filename in a content library of the vCenter or upload it to a datastore that the VMware Aria Suite Lifecycle VM can access. After uploading the ISO file, attach the ISO to the CD-ROM device of the VMware Aria Suite Lifecycle VM by editing the hardware configuration from the vCenter inventory of the VM. From the VMware Aria Suite Lifecycle UI, select the CD-ROM based upgrade option, and then click proceed.
Issue with releasing custom forms without cloud templates.
If a custom form is released without a cloud template in the target VMware Aria Automation environment, even if the release is successful on VMware Aria Suite Lifecycle, the custom form is not visible at the target VMware Aria Automation environment.
Workaround: To release a custom form, ensure that the associated composite cloud template is released or created first on the target VMware Aria Automation.
Managing renamed VMware Aria Automation content types.
Renamed content types must be recaptured from the VMware Aria 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.
No workaround.
Snapshots for VMs remain in the in-progress state in VMware Aria Suite Lifecycle.
Snapshots for VMs that have device back up are not supported and remain in the in-progress state in VMware Aria Suite Lifecycle. You cannot take snapshots of VMs that have a device back up in vCenter. VMware Aria Suite Lifecycle also supports taking snapshots of VMs. However, the vCenter also supports taking device back up. For such VMs, VMware Aria Suite Lifecycle snapshot requests would remain in progress.
No workaround.
VMware Aria Operations upgrade fails.
VMware Aria 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 VMware Aria Operations nodes, this causes the VMware Aria Operations cluster to be offline.
No workaround.
Upgrade Planner and Compatibility Matrix are currently unavailable for VMware Aria rebranded products.
Upgrade Planner and Compatibility Matrix are being revamped to support new VMware Aria rebranding but are currently unavailable for VMware Aria rebranded products.
Workaround: Use this link to check interoperability between various VMware products.
Not all passwords are shown in the VMware Aria Suite Lifecycle locker.
In the VMware Aria Suite Lifecycle locker, only 10 passwords are shown.
Workaround: Using the password alias, the user can search for the password. Alternatively, the user can also retrieve all passwords by using the public API.
Adding a standalone Automation Config deployment as an endpoint to VMware Aria Automation, will cause the inventory sync to fail
When an inventory sync is initiated in VMware Aria Automation, the request identifies it's Automation Config associations.When the Automation Config is added to VMware Aria Automation outside Aria Lifecycle Manager, you will see a failed Import request in the Aria Lifecycle Manage requests page for the Automation Config.Cause:The additional configuration steps performed during the deployment of an Automation Integrated Automation Config are not executed when a standalone Automation Config is added to VMware Aria Automation.Note: It is recommended to deploy Automation Integrated Automation Config only using VMware Aria Suite Lifecycle
Workaround: Remove the integration created in Aria Automation and deploy Automation Integrated Automation Config using Aria Suite Lifecycle
Do not use VMware Repository option when upgrading Orchestrator.
The vRealize Orchestrator application cannot be upgraded to VMware Aria Automation Orchestrator 8.12.x by using the VMware Repository option. This option is intended for internal test and is not functional for external users.
Workaround:
When upgrading the vRealize Orchestrator application to VMware Aria Automation Orchestrator 8.12.x in the Environments section of the Lifecycle Operations service of VMware Aria Suite Lifecycle, select either VMware Aria Suite Lifecycle Repository or Repository URL as the Repository Type option. Do not select the VMware Repository option.
VMware Aria Operations deployment with cloud proxy is failing for cloud proxy node.
When a cloud proxy is involved in VMware Aria Operations deployment, the deployment fails to assign an IP address for the cloud proxy node, and the node is unable to join the cluster, because the fetch call is using an outdated cloud proxy name.
Workaround:
This issue has been resolved in VMware Aria Suite Lifecycle 8.12 Patch 1. The Patch allows VMware Aria Suite Lifecycle to correctly call the renamed VMware_Aria_Operations_Cloud_Proxy when fetching OVF properties. To avoid the issue, use VMware Aria Suite Lifecycle 8.12 Patch 1.
Lack of minimum free disk space causes legacy-based product upgrade to fail.
Upgrading to VMware Aria Suite Lifecycle 8.12 from legacy versions fails if the free disk space for the root partition is less than 3 GB.
Workaround: Maintain 3 GB of free disk space for the '/' partition and verify that you have this amount of free disk space before you start the upgrade to VMware Aria Suite Lifecycle 8.12 and later versions. See KB 92294.
Unable to download VMware Aria Automation 8.12.0 install binary.
You are unable to download VMware Aria Automation 8.12 from MyVMware in VMware Aria Suite Lifcycle 8.12.0.
Workaround: The install binary for VMware Aria Automation 8.12.0 can be downloaded manually from the MyVMware Customer Connect portal in either the NFS Location or VMware Aria Suite Lifecycle 8.12.0 Appliance. Afterwards, the install binary can be mapped in the VMware Aria Suite Lifecycle 8.12.0 user interface from the Settings>Product Binaries page. In the MyVMware Customer Connect portal, the binary is named Prelude_VA-8.12.0.30728-21622235_OVF10.ova.
APUAT assessment report is blank when running APUAT assessment tool to upgrade the existing vRealize Operations environment to VMware Aria Operations 8.12.0.
When running a APUAT assessment for starting a product upgrade from vRealize Operations 8.x to VMware Aria Operations 8.12.0, the generated assessment report is blank.
Workaround: You can continue with the upgrade, but the generated assessment report is blank. This known issue is expected to be resolved in a future release of VMware Aria Suite Lifecycle.
The following issues have been resolved:
Note: For additional resolved issues for this release, see VMware Aria Suite Lifecycle 8.12 Product Support Pack Release Notes.
Certificate references products in Locker -> Certificates UI not shown.
When upgrading from vRSLCM v8.8.x to vRSLCM v8.10.x, certificate references of products are not shown in the Locker -> Certificates UI. The issue has been observed with VMware Identity Manager and VMware vRealize Automation/VMware Aria Automation products.
This has been fixed in VMware Aria Suite Lifecycle 8.12. To resolve the issue, you must perform an inventory sync of all impacted products after upgrading to VMware Aria Suite Lifecycle 8.12.
