NSXT Password expired on v12-ClusterReady-0.5 template - May effect all ClusterReady, PksInstalled & NsxtReady templates #684
Labels
AppliesTo/vAppTemplate/v12-Baseline
Apply for template but not version specific updates
AppliesTo/vAppTemplate/v12-ClusterReady
Apply for template but not version specific updates
AppliesTo/vAppTemplate/v12-NsxtReady
Apply for template but not version specific updates
AppliesTo/vAppTemplate/v12-PksInstalled
Apply for template but not version specific updates
AppliesTo/vAppTemplate
Only use if you are unsure if L1 or L2 related
bug/major
Error in guide or lab template that impact ALL USERS
state/inProgress
WorkaroundAvailable
The password for NSX-T Manager in the clusterReady-0.5 template has expired. This is a bug, the password expiration timer should have been adjusted in the saved template, and I will publish an updated ClusterReady-0.6 Template soon, until then please use the workaround below.
Please note, PKS will not properly boot until the NSX Manager password has been fixed per the workaround below.
Load a ClusterReady 0.5 template and RDP into control center. Log into vcenter, and as soon as NSX-Manger has booted up, open a remote console to the nsx manager VM from vcenter.
Login to nsxt manager prompt with username: admin password: VMware1!VMware1!
After you login, you will be prompted to change the password, enter new password: TmpPasswd1!TmpPasswd1!
NOTE: you are not done, the lab will not work unless you complete the remaining steps.
Enter the command
set user admin password TmpPasswd1!TmpPasswd1!
you will be prompted to enter the current password - PLEASE NOTE - at this time the current password is still VMware1!VMware1! as the new password you entered when prompted at login does not permanently apply until you enter this command.Enter the command
exit
at the prompt to log out, and log back in again with username: admin password: TmpPasswd1!TmpPasswd1!Enter the command
set user admin password VMware1!VMware1!
, you will be prompted to enter your current password: TmpPasswd1!TmpPasswd1!Enter the command
exit
at the prompt to log out, and log back in again with username: admin password: VMware1!VMware1!Now that you have refreshed the working password back to its original value, the PKS deployment can complete. Because this problem prevents PKS from booting up properly, the PKS and K8s cluster startup sequence cannot complete until you have made this update, and it could take an additional 30-60 minutes after you have completed the above steps for PKS to fully recover.
The text was updated successfully, but these errors were encountered: