Error: "VCF Operations Fleet Management is Not Ready" or "Management Lifecycle is Not Ready" when secure token expires
search cancel

Error: "VCF Operations Fleet Management is Not Ready" or "Management Lifecycle is Not Ready" when secure token expires

book

Article ID: 419086

calendar_today

Updated On:

Products

VCF Operations VMware vSphere ESXi

Issue/Introduction

There is a discrepancy in status reporting between the VCF Operations UI and the Fleet Manager Lifecycle UI. The VCF Operations Admin UI indicates that Fleet Management is connected, but the Fleet Management > Lifecycle > VCF Management shows either status:

  • VCF Operations Fleet Management is Not Ready

  • Management Lifecycle is Not Ready

Environment

  • VCF Operations 9.0.0.0, 9.0.1.0

  • VCF Fleet Manager 9.0.0.0, 9.0.1.0

Cause

The secure token, which VCF Operations issues to the Fleet Manager component for connectivity, is not automatically rotating as expected before its 90-day expiration. When the token expires, the Lifecycle UI loses connection.

Resolution

This issue is resolved in VCF Operations 9.0.2.0. 

Workaround 1

Restart the lifecycle service to temporarily re-establish the connection.

  1. SSH to the Fleet Manager node. 

  2. Run the command:
    • systemctl restart vrlcm-server.service

  3. Wait a few minutes for the service to settle, then refresh the Lifecycle UI in VCF Operations. 

  4. If the connection fails again after a short period, proceed to the Workaround 2 section below. 

Workaround 2

Use the following procedure to manually drop the expired key from the database and restart the lifecycle service.

  1. Snapshot the VCF Operations cluster

  2. Log out of the VCF Operations user interface (UI).

  3. SSH to the VCF Operations Master or Replica node.

  4. Open a connection to the PostgreSQL central database by running the following command:
    • su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433"

  5. Drop the expired key by running the following command in the database shell:
    • delete from kv_ops_signing_keys;

  6. SSH to the Fleet Manager  node.

  7. Restart the lifecycle service:
    • systemctl restart vrlcm-server.service

  8. Wait a few minutes for the services to settle, then refresh the Fleet manager UI in VCF Operations.