vRA upgrade failing deploying vro services from 8.6.2 to 8.11 when using the SOAP plug-in.

Products

• VMware Aria Suite

Issue/Introduction

To get the vRA upgraded to 8.11 successfully.

Symptoms:

• The following error is present on the /var/log/vmware/prelude/upgrade-<date>.log

  [ERROR][2023-03-15 21:56:07][vranode1.domain.com][Exit Code: 123] Error while deploying infrastructure and application services.

   

• VCO pods fail to come up /var/log/vmware/prelude/deploy-<date>.log

[2023-03-15 21:53:02] ERROR Release 'vco' in namespace 'prelude' failed to come up
Traceback (most recent call last):
  File "/opt/scripts/helm-upstall", line 286, in main
    helm_wait(namespace, release_name, timeout=timeout)
  File "/opt/scripts/helm-upstall", line 127, in helm_wait
    helm_wait_check()
  File "/opt/python-modules/vracli/decorators.py", line 161, in wrapper
    raise RuntimeError(f'retry timeout exceeded for {f_name}') from err
RuntimeError: retry timeout exceeded for helm_wait_check
+ result=1
+ set +x
Exit code of install/update of release vco is 1
+ return 1
[2023-03-15 21:53:03] ERROR Release 'approval-service' in namespace 'prelude' failed to come up
Traceback (most recent call last):
  File "/opt/scripts/helm-upstall", line 286, in main
    helm_wait(namespace, release_name, timeout=timeout)
  File "/opt/scripts/helm-upstall", line 127, in helm_wait
    helm_wait_check()
  File "/opt/python-modules/vracli/decorators.py", line 161, in wrapper
    raise RuntimeError(f'retry timeout exceeded for {f_name}') from err
RuntimeError: retry timeout exceeded for helm_wait_check
+ result=1
+ set +x

 

• The orchestrator logs will show the following error /services-logs/prelude/vco-app/files-logs/vco-server-app.log:

2023-03-15T20:42:06.753Z ERROR vco [host='vco-app-7bddb8b94b-ns6z9' thread='ApplicaitonEventHandler-1' user='' org='' trace=''] {} com.vmware.o11n.plugin.soap.axis2.Axis2SOAPAdaptor - Unable to load content of the WSDL and its schemas for '009453c9-1fc5-4355-8df3-0f3bcd016cbf', WSDL content: <?xml version='1.0' encoding='UTF-8'?><!-- Published by JAX-WS RI (http://jax-ws.java.net). RI's version is JAX-WS RI 2.3.0-b170407.2038 svn-revision#2eaca54d17a59d265c6fe886b7fd0027836c766c. --><!-- Generated by JAX-WS RI (http://jax-ws.java.net). RI's version is JAX-WS RI 2.3.0-b170407.2038 svn-revision#2eaca54d17a59d265c6fe886b7fd0027836c766c. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis -200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:so ap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://management/hpsa/api" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://management/hpsa/ap i" name="HPSAConnectorService">

 

Environment

VMware vRealize Automation 8.x

Cause

This happens due to the unconfigured SOAP plugin adapter on vRO.

Resolution

Workaround is available.

Workaround:
Workaround is to get the SOAP adapter plugin disabled.

Steps:

1. Revert to working snapshot.
2. Login to vRO control center using root credentials.
3. Go to Manage Plugins.
4. Disable plugin SOAP.
5. Take a new snapshot
6. Retry the upgrade.

Additional Information

Impact/Risks:

There is no impact.