Vouch-Noauth And Vouch-Keystone Pods Are Not Ready Due To Token Expiry

Problem

The Vouch-Noauth and Vouch-Keystone pods are not in a ready state in both Infra and Workload regions. This situation is preventing the environments from being fully operational and has resulted in the upgrade being stalled.

Environment

  • Self-Hosted Private Cloud Director Virtualization - v2025.2 to v2025.6

Cause

  • Vouch token stored in consul has expired, and it weren't renewed automatically by the vouch-renew-token cronjob.
  • The issue has been reported as a bug, and the Platform Engineering team tracked it under the ID PCD-1468 and the fix has been released in July release.

Diagnostics

  1. vouch-keystone and vouch-noauth pods become not ready.
Sample Output
Copy
  1. Perform the cURL Test

Steps:

  • Exec in to vouch-keystone pod and get the vault token from keystone.conf
Command
Copy
  • Run the cURL command after replacing the actual token from above output
Command
Copy
Sample Output
Copy

If the token has expired, the output will indicate "Permission denied." as shown above.

Resolution

  • Upgrade to Self-hosted Private Cloud Director July release and above version.

Workaround

  • Manually renew the expired token so that vouch pods can communicate with consul.

Steps:

  1. Get the CONSUL_HTTP_TOKEN from Airctl host [The host with airctl state file is present]
Bash
Copy
  1. Exec into decco-consul-consul-server pod in default namespace
Command
Copy
  1. Export the COSUL_HTTP_TOKEN from step 1 in decco-consul-consul-server pod
Command
Copy

The following commands generate a number of outputs that corresponds to the total number of regions present in the environment.

  1. Retrieve region UUIDs.
Command
Copy
  • The <REGION_UUID> serves a crucial role in distinguishing between multiple regions. This unique identifier ensures that each region can be clearly identified and managed effectively within your environment.
Sample Output
Copy
  1. Retrieve existing tokens
Command
Copy
Sample Output
Copy
  1. Delete the existing Token for the specified affected region(s).
Command
Copy
Sample Output
Copy

Exit from the decco-consul-consul-server pod

  1. Manually run the vouch-renew-tokenJob

Repeat this step for all affected regions by changing the <AFFECTED_NS>

Command
Copy
  1. Check if theVouch-keystone and Vouch-noauth back healthy
Command
Copy
  • If these steps prove insufficient to resolve the issue, reach out to the Platform9 Support Team for additional assistance.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard