QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Kind reminder that after one week there is not feedback provided here or in Slack and it is a high priority ticket.
Please share your thoughts in today's retro.

There was a slack thread about this on friday: https://suse.slack.com/archives/C02CLB2LB7Z/p1737126172158479

First test run failed with "You need to register SLE 16 Beta", so I've put back the registration code in the jsonnet profile.

rainerkoenig wrote in #note-5:

First test run failed with "You need to register SLE 16 Beta", so I've put back the registration code in the jsonnet profile.

official job group cannot use registration at the moment but agama.install_url in bootloader params so we can have results for B1.

Agama is giving me a hard time again. It complains that the product must be registered, but it also complains that I provide a registration code....
https://suse.slack.com/archives/C082VE1U2F5/p1737554948986869

I see your comment, I see the sles_default_unattended job that I passed without problems and that I cloned my VR from, only exchanging the agama_profile and the YAML schedule to handle the encrypted boot. And my VR fails. And I don't understand why, because all what I added was a storage section to the profile.

PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21033

VR now works, but I had to create an own module for enrypted lvm, because here the encryption password is only pulled once before grub and there is no encryption password for swap.

Verification runs for all architectures passed now. s390x was difficult, had to provide 3 variables get `boot_encrypt? functional.
WIP removed from the PR now.

rainerkoenig wrote in #note-10:

Verification runs for all architectures passed now. s390x was difficult, had to provide 3 variables get `boot_encrypt? functional.
WIP removed from the PR now.

Please add validation for "encryption" too.

Additionally, as only minor changes are required to your PR you can already start the setup of this test suite in job group yaml so we can have it for B1.

Merged, please setup the test suite in product job group (right now there is some connectivity issues but just put them there, we will check tomorrow).