Container and provisioning-service are blank or not REGISTERED after applying vRA 7.6 Patch 25 or above
search cancel

Container and provisioning-service are blank or not REGISTERED after applying vRA 7.6 Patch 25 or above

book

Article ID: 325937

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Services failing to register can place the environment into a non-functional state.

Symptoms:
  • After applying Cumulative Update for vRealize Automation 7.6 Patch #25 and above, the container-service and provisioning-service appears blank and not REGISTERED under the VAMI > Services tab
  • Requests to https://ApplianceFQDN/container-service/api/status returns a 404 Not Found error
  • No log messages are recorded indicating a failure.


Environment

VMware vRealize Automation 7.6.x

Cause

In some air gapped environments with no internet connection, during the loading of XML resources, one of the used libraries (Spring Framework) makes a request to www.springframework.org which does not fail nor throws a timeout.  This blocks further loading of these specific services.

Resolution

See the Workaround section for additional details.

Workaround:

Prerequisites

  • Please take simultaneous non-memory snapshots of each virtual appliance(s) in the cluster.
  • You have access to root user and password
  • You have SSH or console access to each virtual appliance.

Procedure

  1. SSH / PuTTy into each virtual appliance impacted by this issue in the cluster
  2. Edit the /etc/hosts file and append the following to the end
    127.0.0.1 www.springframework.org
  3. Restart the vcac-server service on each node
    service vcac-server restart