When using SSH to connect to a node via the vmware-system-user account, it has expired
1.23.x
1.24.x
The VMware-system-user password is set to expire in 60 days as part of STIG Hardening.
If the Guest Cluster's API server is unresponsive, the pass_expiry will not be applied.yaml noted in the resolution, which will prevent the correction of the VMware-system-user account. This presents a condition where the API server cannot be corrected because the SSH account is locked, and the account can't be corrected because the API server is down.
To correct this condition, it is required to reboot the Guest Cluster nodes and boot into the grub menu via the VM Console, which will allow the user to clear expiration on the vmware-system-user account.
linux /boot/vmlinuz-4.19.283-3.ph3-esx root=UUID=####-####-####-####-############ rw init=/bin/bashchage -l vmware-system-userchage -m 0 -M -1 vmware-system-userchage -l vmware-system-userreboot -f
This needs to be done on all the control plane nodes in the Guest Cluster, one at a time. After performing the steps on the first control plane node, please wait for it to restart and obtain an IP address. Post that, proceed with the remaining control plane nodes one at a time.
Bypass Containerized Permissions by accessing the vm directly through the ESXi interface. In some cases, editing the Boot Delay of a VM is necessary, typically when adding resources to a powered-off VM.