Introduction

What's New

Salt Minion Configurations
Ability to Install and Upgrade a Salt Minion in VMware Aria Suite Lifecycle
Configure Salt Minion to point to a Salt Master and add Grains
Migration Service
Migrate VMware Aria Operations Saas content to On-Prem
VMware SSO Integration
Integrate VMware Aria Operations, Logs and Orchestrator with embedded VMware SSO in vCenter
Configurable during Day-0 and Day-N
Import of a product configured with VMware SSO
Supports only versions above 8.18.0
Content Management
Capture and Deploy content to source control using tags
VMware Aria Operations Enhancements
VMware Aria Operations Upgrade would be based on 2 pak files
Snapshots on VMware Aria Operations Cloud Proxy will not be taken during upgrade of VMware Aria Operations
My VMware or Customer Connect features deprecated

Known Issues

Unable to trigger VMware Aria Suite Lifecycle upgrade to 8.18.0
Following a successful upgrade precheck and the submission of the upgrade request for VMware Aria Suite Lifecycle, users are redirected back to the System Upgrade page without any accompanying information. When inspecting /var/log/vmware/capengine/core-engine.log you see an exception stating "
Error in executing request. Error: Operation not allowed in the current state of workflow".
In order to fix this issue follow the steps mentioned in the KB article: https://kb.vmware.com/s/article/96749
Product Deployment and Day-2 Operations failure due to SHA1 weak ciphers/algorithms removal from VMware Aria Suite Lifecycle
After applying VMware Aria Suite Lifecycle 8.14 Patch 1, you may encounter deployment and day-2 operation failures, attributed to the elimination of weak algorithms in Suite Lifecycle. To prevent such issues, it is recommended to either turn on FIPS in VMware Aria Suite Lifecycle or implement the specified workarounds on other VMware Aria Products, as outlined in the KB 95835.
Sample Exception : InvalidKeySpecException: key spec not recognized
Upgrade fails with the message "The /dev/sda4 partition has insufficient free disk space"
During the upgrade process, a precheck runs to verify available disk space on
/partition
. In environments where the disk space is less than 3 GB, the upgrade might fail with an insufficient free disk space error in the Aria Suite Lifecycle Manager UI.
Workaround
: To proceed with the upgrade, you must clear the disk space on
/partition
. See https://kb.vmware.com/s/article/95238.
Splash Icon in VMware Aria Suite Lifecycle login page does not appear in Firefox browser
This is a cosmetic issue. The graphic on the login page is not rendered.
Build versions are not updated following upgrade
After upgrading VMware Aria Suite Lifecycle 8.12 to 8.18, the version and build number are not updated under
Lifecycle Operations
>
Settings
>
System Details
and post-update scripts do not execute completely.
Workaround
: You can take steps to address this issue before or after upgrading.
Before upgrading, check the for the file
/var/log/bootstrap/fips_disable
.
If you find the file, proceed with the upgrade.
If you do not find the file:
Create the file:
touch /var/log/bootstrap/fips_disable
.
Change permissions:
chmod 644 /var/log/bootstrap/fips_disable
.
Proceed with the upgrade.
If you encounter the issue after upgrading, follow the steps in https://kb.vmware.com/s/article/95231.
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.
Customization Spec check-in to source control using Content Management is not supported
After a customization spec is captured from a vSphere endpoint, checking it into source control is not supported.
No Workaround.
Bulk Script Execution from Global level is not supported for tenanted products
Script execution as a Day-2 action is not valid for products with tenants such as VMware Aria Orchestrator and VMware Aria Automation Config.
Capture & Deploy actions against VMware Aria Operations 8.14 when FIPS mode is enabled fails
No Workaround
Adding a standalone Automation Config deployment as an endpoint to VMware Aria Automation causes the inventory sync to fail
When an inventory sync is initiated in VMware Aria Automation, the request identifies its Automation Config associations. When Automation Config is added to VMware Aria Automation outside of VMware Aria Lifecycle Manager, you will see a failed import request on the VMware Aria Lifecycle Manager requests page for the Automation Config. The reason for the failure is that the additional configuration steps performed during the deployment of a VMware Aria Automation integrated with Automation Config are not executed when a standalone Automation Config is added to VMware Aria Automation.
Workaround:
Remove the integration created in VMware Aria Automation and use VMware Aria Suite Lifecycle to deploy VMware Aria Automation integrated with Automation Config. NOTE: This is a recommended best practice when deploying VMware Aria Automation integrated with Automation Config,
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, the custom form will not be visible in the target VMware Aria Automation environment even if the custom form appears successfully released in VMware Aria Suite Lifecycle.
Workaround:
Before releasing a custom form, ensure that the associated composite cloud template has been released or created first in 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, then check out the content from the source control endpoints.
No workaround.

Product Support Notices

Deprecation of localized languages
Beginning with the next major release, we will be reducing the number of supported localization languages. The three supported languages will be:
Japanese
Spanish
French

The following languages will no longer be supported: Brazilian Portuguese, German, Italian, Korean, Simplified Chinese, Traditional Chinese.
Impact:
Users who have been using the deprecated languages will no longer receive updates or support in these languages.
All user interfaces, help documentation, and customer support will be available only in English or in the three supported languages mentioned above.