TKGi MC update caused unexpected behaviour and a second Opsman creation.

Products

• VMware Tanzu Kubernetes Grid Integrated Edition

Issue/Introduction

After successfully completed upgrade and the Opsman Director TKGi and harbor tiles were upgraded to respective MC version 1.18.5 

We realised that we had to complete a small change in the MC 

We have completed the change from the MC configuration and apply the configuration, but this operation have failed during Opsman Deployment 

 

We have checked we have two Opsman VMs and we could see that the new Opsman have a different Password from the old one and is not fully configured.

 

We have brought back the old 1.17 MC to retrieved the old password. 

Powered off the new Opsman that was deployed and logged in to the Opsman that was deployed successfully with 1.18.5 with the correct password. 

 

We can see that Opsman Director TKGi and harbor VMs are all up and running and the foundation is stable.

 

 

Environment

TKGi with Management console upgraded to 1.18.5

Pending cluster upgrade

Cause

A mismatch in the database occurred during the update operation

Resolution

Please contact support for assistance to prevent unexpected behaviour and loss of data