VMware Aria Suite Lifecycle 8.14 Patch 1 Day 2 operations fail for VMware Aria Automation with error code LCMVRAVACONFIG590024
Article ID: 326084
Updated On:
Products
VMware Aria Suite
Issue/Introduction
Symptoms:
- Day 2 actions for VMware Aria Automation fails with the following error.
Error Code: LCMVRAVACONFIG590024 VMware Aria Automation hostname is not valid or unable to run the product specific commands via SSH on the host. Check if VMware Aria Automation is up and running. VMware Aria Automation hostname is not valid or unable to run the product specific commands via SSH on the host. Check if VMware Aria Automation is up and running. com.vmware.vrealize.lcm.drivers.vra80.exception.VraVaProductNotFoundException: Either provided hostname: <VMwareAriaAutomationFQDN> is not a valid VMware Aria Automation hostname or unable to run the product specific commands via SSH on the host. at com.vmware.vrealize.lcm.drivers.vra80.helpers.VraPreludeInstallHelper.getVraFullVersion(VraPreludeInstallHelper.java:970) at com.vmware.vrealize.lcm.drivers.vra80.helpers.VraPreludeInstallHelper.checkVraApplianceAndVersion(VraPreludeInstallHelper.java:978) at com.vmware.vrealize.lcm.drivers.vra80.helpers.VraPreludeInstallHelper.getVraProductDetails(VraPreludeInstallHelper.java:754) at com.vmware.vrealize.lcm.plugin.core.vra80.task.VraVaImportEnvironmentTask.execute(VraVaImportEnvironmentTask.java:145) at com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158) at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)Environment
VMware Aria Suite Lifecycle 8.14.x
VMware Aria Automation 8.x
VMware Aria Automation 8.x
Cause
This is a known issue reported in the VMware Aria Suite Lifecycle 8.14 Patch 1 Release Notes. See 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 article Steps for Removing SHA1 weak Algorithms/Ciphers from all VMware Aria Products.
Sample Exception:
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 article Steps for Removing SHA1 weak Algorithms/Ciphers from all VMware Aria Products.
Sample Exception:
InvalidKeySpecException: key spec not recognized.
Resolution
Follow the article Steps for Removing SHA1 weak Algorithms/Ciphers from all VMware Aria Products or alternatively follow the steps indicated in the workaround section.
Workaround:
Workaround:
Prerequisites
- Validate you have valid backups or temporary snapshots of VMware Aria Suite Lifecycle before proceeding.
Procedure
- Log in to VMware Aria Suite Lifecycle.
- Navigate to Lifecycle Operations > Settings > System Details.
- Check the option Enabled on FIPS Mode Compliance and then click on UPDATE (this will restart VMware Aria Suite Lifecycle services).
- After the services restart, retry the VMware Automation day 2 action.
- Revert the changes by disabling the FIPs Mode Compliance located at Lifecycle Operations > Settings > System Details and then click on UPDATE to restart the services.
Feedback
Yes
No
Powered by
