This is failing openQA tests because it's broken something we do in some of those tests. We need the root account to have a password on the install system for the post-install tests to work. The Workstation live installer does not let you set a password for the root account during install, so after the install is complete - but with the installer still running - we go to a console and run "echo 'root:weakpassword' | chpasswd -R /mnt/sysimage" . This should set the root password in the installed system to "weakpassword", and has worked for years. But with this update it fails, saying:
chpasswd: (user root) pam_chauthtok() failed, error:
Authentication token manipulation error
chpasswd: (line 1, user root) password not changed
That obviously breaks the test, because on reboot, it can't log in as root as it expects to. This does seem like a bug.
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This is failing openQA tests because it's broken something we do in some of those tests. We need the root account to have a password on the install system for the post-install tests to work. The Workstation live installer does not let you set a password for the root account during install, so after the install is complete - but with the installer still running - we go to a console and run
"echo 'root:weakpassword' | chpasswd -R /mnt/sysimage"
. This should set the root password in the installed system to "weakpassword", and has worked for years. But with this update it fails, saying:That obviously breaks the test, because on reboot, it can't log in as root as it expects to. This does seem like a bug.
This update has been unpushed.