vCenter plugin connection becomes unusable after reboot of vCenter in VCF Operations Orchestrator

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In VCF Operations Orchestrator 9.1.0.0 environments, the connection to vCenter Server is lost following a vCenter Server reboot. The vCenter Server instance is marked as disconnected in the inventory, and workflows dependent on the vCenter plugin fail with the following error in vco-server-app.log:

SDK in bad health: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException

Environment

VCF Operation Orchestrator 9.1.0.0

Cause

This behavior is a confirmed product defect in VCF Operations Orchestrator 9.1.0.0. The vCenter plugin fails to properly re-initialize and re-authenticate SDK connection credentials automatically after a vCenter Server restart.

Resolution

This issue is targeted to be fixed in VCF Operations Orchestrator 9.1.1 and higher.

Once the fix is released, upgrade VCF Operations Orchestrator to the resolved version. See Download Broadcom Products and Software for steps to download the release.

For defects and enhancements, it is recommended to subscribe to this article to be updated on fix status.

Workaround

If connectivity is lost after a vCenter Server reboot, perform the following steps to manually restore the connection:

1. Log in to the VCF Operations Orchestrator.
2. Navigate to Inventory.
3. Locate the vCenter Server instance that is disconnected.
4. Run the Update a vCenter Server instance workflow.
5. Complete the workflow wizard to re-authenticate and refresh the SDK connection.