This is a known issue affecting Cloud Director Availability 4.4.x.
Currently, there is no resolution.
Workaround:
To work around this issue, update the system-password file on the Cloud Director Availability appliance to properly enforce the password complexity requirements.
- SSH to the Cloud Director Availability appliance.
- Log in as root using the password that was rejected initially.
- Take a backup of the system-password file:
cp /etc/pam.d/system-password /etc/pam.d/system-password.old
- Use a text editor, such as vim, to edit the /etc/pam.d/system-password file to look as follows:
# Begin /etc/pam.d/system-password
password requisite pam_pwhistory.so retry=3 remember=5 enforce_for_root
password requisite pam_pwquality.so dcredit=-1 ucredit=-1 lcredit=-1 ocredit=-1 minlen=8 minclass=4 difok=4 retry=3 maxsequence=0 enforce_for_root
password required pam_unix.so sha512 shadow use_authtok
# End /etc/pam.d/system-password
- Save the changes to the system-password file.
- Change the password to a sufficiently complex one using the passwd command or through the UI.