InvalidKeySpecException: key spec not recognized error when upgrading Aria Automation 8.13.1, Aria Operations for Logs and Aria Operations for Network with Aria Suite Lifecycle 8.16

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Upgrading Aria Automation environments from Aria Automation 8.13.1 with Aria Suite Lifecycle 8.16 you receive the error:

Error Code: LCMVRACONFIG50008 Check VMware Aria Automation hostname is resolvable and reachable. Check VMware Aria Automation hostname is resolvable and reachable. com.vmware.vrealize.lcm.common.exception.userinput.vra.VraVamiHostNameInvalidException: Unable to run command + vracli upgrade status --json . Ensure the VMware Aria Automation VA host <Hostname> is reachable. at com.vmware.vrealize.lcm.drivers.vra80.helpers.VraPreludeInstallHelper.checkUpgradeStatus(VraPreludeInstallHelper.java:495)

• Upgrading Aria Operations for Logs 8.12.x and 8.14.x with Aria Suite Lifecycle 8.16 you receive the error:

Error Code: LCMVRACONFIG40004 Invalid hostname provided for VMware Aria Operations for Logs. Invalid hostname provided for VMware Aria Operations for Logs. com.vmware.vrealize.lcm.vrli.plugin.VrliImportEnvironmentTask.exception.VrliInvalidHostException: Cannot execute ssh commands. Exception encountered : Session.connect: java.security.spec.InvalidKeySpecException: key spec not recognized
        at com.vmware.vrealize.lcm.plugin.vrli.VrliImportEnvironmentTask.execute(VrliImportEnvironmentTask.java:342) [vmlcm-vrliplugin-core-8.12.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:63) [vmlcm-engineservice-core-8.12.0-SNAPSHOT.jar!/:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
        at java.lang.Thread.run(Unknown Source) [?:?] 

• The /var/log/vrlcm/vmware_vrlcm.log contains an InvalidKeySpecException similar to:

2024-03-05 09:46:58.173 ERROR [pool-3-thread-18] c.v.v.l.u.SessionHolder -  -- SessionHolder.newSession Exception encountered
com.jcraft.jsch.JSchException: Session.connect: java.security.spec.InvalidKeySpecException: key spec not recognized
        at com.jcraft.jsch.Session.connect(Session.java:550) ~[jsch-0.2.13.jar!/:0.2.13]
        at com.vmware.vrealize.lcm.util.SessionHolder.newSession(SessionHolder.java:53) [lcm-util-8.16.0-SNAPSHOT.jar!/:?]

Environment

VMware  Aria Suite Lifecycle 8.16.0
VMware Aria Automation 8.13.x

VMware Aria Operations for Logs 8.12.x and 8.14.x

VMware Aria Operations for Network 8.9.0

Cause

The issue occurs due to a vulnerability fix on recent Aria Suite Lifecycle versions.

Resolution

Despite the error the upgrade itself proceeds in Aria Automation and left unattended will likely complete successfully. The upgrade can be monitored manually from the Aria Automation appliances using command

vracli upgrade status --follow

Once completed a retry issued on the failed upgrade request in Aria Suite Lifecycle will mark the upgrade as successful.

Workaround:

To workaround the issue enable FIPS Mode Compliance on Aria Suite Lifecycle Manager:

Note: VMware Aria Suite Lifecycle restarts when you activate or deactivate FIPS Mode Compliance.

1. From My Service dashboard, select Lifecycle Operations and then select Settings.
2. On the System Administration page, click System Details.
3. Activate or deactivate the FIPS Mode Compliance check box and then click UPDATE.