Remediation fails for Fleet Manager in VCF Operations with error "Remediate for appliance has failed"

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The Fleet Management root password is in a disconnected state under VCF Operations password management
• The password in use is good - not locked or expired
• All remediation attempts fail with error "Remediate for appliance has failed"
• The failure is instantaneous and no concurrent password management task is created on the VCF Operations UI.
• Implementing KB 422906 does not resolve the issue
• The vcops-bridge.log has entries similar to:

2026-05-22T10:19:42.064Z ERROR vcfops-bridge 2783130 [ops@4413 threadId="1002" threadName="ServerConnection on port 10000 Thread 11"] [com.vmware.vcops.bridge.server.vcf.password.task.PasswordTaskOrchestrator.remediatePassword] - Password key xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx not found.

 

Environment

VCF 9.0.x

Cause

This is caused by duplicate entries in the kv_vcf_password_account_data table in the VCF Operations database with same password resource key.

Resolution

1. Make a note of the Password key referenced in the vcops-bridge.log

e.g.  Password key xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx not found.

2. NOTE: Before proceeding bring the VCF Operations cluster offline and create snapshots of all nodes. Once done, bring the cluster online again and wait until the cluster status is stable and collecting. See KB 342576 on the process - DO NOT SKIP THIS STEP

3. SSH to the VCF Operations master node

4. Connect to the database:

su admin -c "$VMWARE_VPOSTGRES_ROOT/bin/psql -h localhost -U vcops -d vcopsdb -p 5433"

5. Run the following query:

select * from kv_vcf_password_account_data where passwordresourcekey = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx';

6. Confirm there is more than one entry associated with that passwordresourcekey

7. Once confirmed, truncate the table:

truncate table kv_vcf_password_account_data;

8. Quit the database:

\q

9. Restart the collector service on VCF Operations:

service collector restart

(NOTE: This can take a few minutes)

10. Try the remediation again.