OpsManager fails to create bosh deployment due to incorrect credentials or locked account

Products

• Operations Manager

Issue/Introduction

After configuring the OpsMan Tile,
Deployment of bosh is failing with the following error:

------------------ Started deploying Creating VM for instance 'bosh/0' from stemcell 'sc-0c8781ca-b8fc-4595-a00e-eeed33d60cfb'... Failed (00:00:21) 
Failed deploying (00:00:21) Cleaning up rendered CPI jobs... 
Finished (00:00:00) Deploying: Creating instance 'bosh/0': Creating VM: Setting VM metadata to map[created_at:2022-03-25T08:58:24Z deployment:p-bosh director:bosh-init index:0 instance_group:bosh job:bosh name:bosh/0]: CPI 'set_vm_metadata' method responded with error: CmdError{"type":"Unknown","message":"The credentials were incorrect or the account specified has been locked.","ok_to_retry":false} Exit code 1 

Environment

Product Version: 2.10

Resolution

This issue is happening when NSX-T Policy API  is selected and Principal Identity(Certificate authentication) is used.

There are 4 modes that you can connect to NSX-T manager:

1. NSX-T manager API  with Username/password - WORKING
2. NSX-T manager API with Certificates(Principal Identity) - WORKING
3. NSX-T Policy API with username/password - WORKING
4. NSX-T manager API with Certificates(Principal Identity) -  NOT WORKING

Workaround: use one of the 3 working API modes.

Engineering is aware about this issue and they working for the fix. At the moment of publishing this Knowledge article, a pull request in place. https://github.com/cloudfoundry/bosh-vsphere-cpi-release/pull/322

Ops Manager 2.10.40 fixes this issue.