action #160325
Updated by szarate 2 months ago
## Motivation In https://sd.suse.com/servicedesk/customer/portal/1/SD-150437 we are asked to handle "compromised root passwords in QA segments" including s390zl11…16 ## Goals * **G1:** Autoyast profiles Have an s390x kvm (or any other svirt backend) openQA installation job with non-default password succeed as far as possible * **G2:** Identify which follow-up steps need to be done to fully support non-default passwords in `os-autoinst-distri-opensuse/data` have variables instead of nots3cr3t password such scenarios ## Suggestions In theory, * os-autoinst-distri-opensuse in principle supports using a different password, see https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/main_common.pm#L165 * Clone a default s390x kvm openQA installation job https://openqa.suse.de/tests/13875911 from this should be fairly straightforward, however, there are cases where scenario https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online&machine=s390x-kvm&test=default&version=15-SP6 but with `PASSWORD=<new_password>` with `<new_password>` being anything you setup temporary and see how far the password is already hashed (i.e, slepos) where we might need to contact people from other areas In the end, test can reach * Fix obvious small problems and identify bigger follow-up tasks * Actually s390x shouldn't really matter that much in this should support the autoyast part of #157555 context, could also be an "svirt" job