QA (public) » openQA Project (public) » openQA Tests (public) » Containers and images

Trying to run these jobs in my "local" instance of openQA

A great idea will be to chain all the WSL jobs with the update one using the method described here.

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: wsl-main+register@win11_uefi
https://openqa.suse.de/tests/9871334#step/firstrun/1

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

I've managed to send the output of a PowerShell command through the COM1, to a better parsing of the script. Pending to check if I can overwrite the same HDD_1 parameter with PUBLISH_HDD_1.

https://openqa.suse.de/tests/9927990
https://openqa.suse.de/tests/9927968

If the update takes too long, it will cause the test to fail. Is there a way to limit this time and force a soft_failure?

https://progress.opensuse.org/issues/105160 is a duplicate of this ticket.

Looks like Microsoft provides a sample script to update the system. It's not intended to be used in production, but we can extract some useful commands from it maybe.

https://learn.microsoft.com/en-us/windows/win32/wua_sdk/searching--downloading--and-installing-updates?redirectedfrom=MSDN

New PR created to use this script as is: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17687

After several days trying to use the script I found, several issues that prevent me from going on. Some of them are:

• In Windows 11, the screen locks due to inactivity. After researching, it does not seem to be so easy to disable this feature through Powershell
• When the flag /RebootToComplete is used to fully automate the installation, the script throws an error. I've dived into Microsoft's Windows Update Agent (WUA) API and looks like the script is using a function that is not defined, or deprecated, or I couldn't find in the reference, which causes it to fail
• After checking with Martin Loviska, it seems that the best way of knowing that the updates have finished is wait_serial with a timeout of 1h, but the script does not outputs anything when finishes so the tests fails

There are two possibilities to have an updated Windows image:

1. To create our own script that REALLY uses serial interface to notify when it has finished, and also learn how to disable "inactivity lock screen" in Win11
2. Periodically download the qcow2 image from OSD, update it manually in a local VM and upload it again

Let's discuss this today in the qe-c standup meeting.

After some workout, the scripts communicates with the worker through the serial interface, so it knows when the update process has ended. These three VRs show good results:

• Windows 10 BIOS
• Windows 10 UEFI
• Windows 11 UEFI

Next step is to export the updated qcow image.

The update process works now. Pending to merge the PR