Aria Automation upgrade fails with 'Error while deploying services' and 'vco-app' pods failing to come up fully
search cancel

Aria Automation upgrade fails with 'Error while deploying services' and 'vco-app' pods failing to come up fully

book

Article ID: 312283

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • Upgrade fails with 'Error while deploying services.'
  • output of 'kubectl -n prelude get pods' shows most pods running but the 'vco-app' pods are only partially running.
  • Checking 'vco'-app' logs we only see below errors:
    • nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.symphony.csp.auth.service.CspClient]: Factory method 'cspClientService' threw exception; nested exception is java.lang.IllegalArgumentException: expected system property https.proxyPort to be a number but got empty string


Environment

VMware Aria Automation 8.x

Cause

The issue occurs when the proxy service has been disabled using command vracli proxy disable. This should not be done unless consulted with VMware. The SOAP plugin requires the http.proxyPort property to be non-empty. If you do not wish to leverage the proxy enable it again with the default settings as per the resolution section.

Resolution

To resolve the issue follow the steps outlined below:

1. If using an external HTTP proxy run the following commands to enable the proxy and restart vRO.
# Enable the proxy
vracli proxy enable
# Appy the change
vracli proxy apply

If there is no need of an external proxy, restore the default proxy configuration.
# Delete the current configuration 
vracli proxy delete
# Set the default configuration
vracli proxy set-default
# Apply changes 
vracli proxy apply 


2. To verify that this reset has worked, execute the following command: 

kubectl -n prelude get secret internet.proxy.port -o json | jq -r .data.'"internet.proxy.port"' | base64 -d

If the reset was successful, it should print 3128 


3. Retry the failed LCM upgrade request with the revert to snapshot option set to 'false'

 

Additional Information

If reverted to pre-upgrade snapshots perform steps 1 to 3 and then initiate the upgrade task.