
For Debian, when the user is prompted to change the password on first login, the strings printed are different from CentOS: Debian prints "Current password" while CentOS prints "(current) UNIX password". This difference cause some Ansible tasks that change password to fail. The same problem was corrected for LDAP in https://review.opendev.org/c/starlingx/ansible-playbooks/+/863699 . One of the cases where the password is changed by Ansible tasks is during bootstrap of a subcloud using Redfish Platform Management Service. Test Plan: PASS: Successfully bootstrap a subcloud using Redfish, checking in the Ansible log that the first password was successfully changed. Closes-Bug: 1996196 Signed-off-by: Joao Victor Portal <Joao.VictorPortal@windriver.com> Change-Id: Id3b47224ceb66f834356a37c5746ca1890f6b6bb
27 lines
863 B
YAML
27 lines
863 B
YAML
---
|
|
# The following are configuration parameters that should be stored
|
|
# in secrets files using Ansible vault.
|
|
#
|
|
# Bootstrap specific parameters stored in the vault must have vault_
|
|
# prefix. The same rule is not applied to Ansible specific parameters.
|
|
#
|
|
|
|
# The following settings could be host specific, in which case they
|
|
# can be placed in the <inventory_hostname>_secrets.yml where
|
|
# applicable.
|
|
vault_admin_username: stx-admin
|
|
vault_admin_password: Boot5trap*
|
|
|
|
# The following settings are usually common to all hosts, in which
|
|
# case they can be placed in the secrets.yml file.
|
|
vault_password_change_responses:
|
|
yes/no: 'yes'
|
|
sysadmin*: 'sysadmin'
|
|
\(current\) UNIX password: 'sysadmin'
|
|
Current password: 'sysadmin'
|
|
(?i)New password: 'Boot5trap*'
|
|
(?i)Retype new password: 'Boot5trap*'
|
|
|
|
ansible_become_pass: Boot5trap*
|
|
ansible_ssh_pass: Boot5trap*
|