QA (public) » openQA Project (public) » openQA Tests (public)

Also please be aware that latest supported Leap is currently 15.2

Technically all migration tests from previous releases (42.X, 15.0, 15.1) could be dropped. Unless QA is willing to help maintaing them.

Thank you

lkocman wrote:

Also please be aware that latest supported Leap is currently 15.2

Technically all migration tests from previous releases (42.X, 15.0, 15.1) could be dropped. Unless QA is willing to help maintaing them.

Technically, yes. As long as they work they should be kept though, they can still show product bugs of actual relevance.

@tjyrinki_suse is leap15.3 GM qcow2 in o3 assets?

https://bugzilla.opensuse.org/show_bug.cgi?id=1196549#c6

upgrade_Leap_15.3_kde : https://openqa.opensuse.org/tests/2243864
upgrade_Leap_15.3_gnome : https://openqa.opensuse.org/tests/2243863

In both cases, it seems that the welcome opensuse doesn't work in the same was as in create_hdd_gnome + create_hdd_kde, should I file a bug?
For the upgrade_Leap_15.3_cryptlvm@uefi, I think there was no qcow2 image created.

I will schedule also the tests mentioned in the bugzilla link :

• zdup-Leap-15.2-gnome
• zdup-Leap-15.2-kde

Is there anything else I'm missing?

I opened two bugs for the issues in opensuse_welcome:
https://bugzilla.opensuse.org/show_bug.cgi?id=1197130
https://bugzilla.opensuse.org/show_bug.cgi?id=1197127

I re-triggered the cryptlvm test and the qcow2 image is now available:
https://openqa.opensuse.org/tests/2246951#downloads
@szarate, could you copy it to the folder with the other qcow2 images? (:

I think that it would be better to fix the way that HDD is being created, instead of adding a workaround in the test, as we see different behaviors in gnome + kde.
For example the similar scenario Leap 15.2 -> Leap 15.4 : https://openqa.opensuse.org/tests/2255751#step/opensuse_welcome/3 works fine, so we could probably try to achieve the same result.
@tjyrinki_suse, @szarate wdyt?

punkioudi wrote:

I think that it would be better to fix the way that HDD is being created, instead of adding a workaround in the test, as we see different behaviors in gnome + kde.

No, the behaviour is identical - opensuse-welcome does not autostart in the upgraded system.

For example the similar scenario Leap 15.2 -> Leap 15.4 : https://openqa.opensuse.org/tests/2255751#step/opensuse_welcome/3 works fine, so we could probably try to achieve the same result.
@tjyrinki_suse, @szarate wdyt?

favogt wrote:

punkioudi wrote:

I think that it would be better to fix the way that HDD is being created, instead of adding a workaround in the test, as we see different behaviors in gnome + kde.

No, the behaviour is identical - opensuse-welcome does not autostart in the upgraded system.

For example the similar scenario Leap 15.2 -> Leap 15.4 : https://openqa.opensuse.org/tests/2255751#step/opensuse_welcome/3 works fine, so we could probably try to achieve the same result.
@tjyrinki_suse, @szarate wdyt?

How is it identical?
Leap 15.2 -> Leap 15.4

• show on next startup is selected : https://openqa.opensuse.org/tests/2255751#step/opensuse_welcome/2
• show on next startup gets unselected : https://openqa.opensuse.org/tests/2255751#step/opensuse_welcome/3

Leap 15.3 -> Leap 15.4

• show on next startup is not selected : https://openqa.opensuse.org/tests/2255543#step/opensuse_welcome/8

Do I see something wrong?

Please be aware of https://progress.opensuse.org/issues/108692 which is supposed to ensure that migrations from prior 15.2 are possible.

punkioudi wrote:

favogt wrote:

punkioudi wrote:

I think that it would be better to fix the way that HDD is being created, instead of adding a workaround in the test, as we see different behaviors in gnome + kde.

No, the behaviour is identical - opensuse-welcome does not autostart in the upgraded system.

For example the similar scenario Leap 15.2 -> Leap 15.4 : https://openqa.opensuse.org/tests/2255751#step/opensuse_welcome/3 works fine, so we could probably try to achieve the same result.
@tjyrinki_suse, @szarate wdyt?

How is it identical?

15.3 -> 15.4 has identical behaviour on GNOME and KDE. The difference is that on GNOME, the test module itself start opensuse-welcome as a (meanwhile obsolete?) workaround for a product bug.

favogt wrote:

punkioudi wrote:

favogt wrote:

punkioudi wrote:

I think that it would be better to fix the way that HDD is being created, instead of adding a workaround in the test, as we see different behaviors in gnome + kde.

No, the behaviour is identical - opensuse-welcome does not autostart in the upgraded system.

For example the similar scenario Leap 15.2 -> Leap 15.4 : https://openqa.opensuse.org/tests/2255751#step/opensuse_welcome/3 works fine, so we could probably try to achieve the same result.
@tjyrinki_suse, @szarate wdyt?

How is it identical?

15.3 -> 15.4 has identical behaviour on GNOME and KDE. The difference is that on GNOME, the test module itself start opensuse-welcome as a (meanwhile obsolete?) workaround for a product bug.

Yes, indeed but I was speaking about its difference with the upgrade Leap15.2 -> Leap 15.4 test results.
In any case, I am preparing a PR to solve the test issue (:

Yes, indeed but I was speaking about its difference with the upgrade Leap15.2 -> Leap 15.4 test results.

Yep. From 15.3 on, opensuse-welcome is installed by default and thus also already disabled in those images. So for future 15.4 -> 15.5 upgrades opensuse-welcome will also not appear after upgrades.

For some reason I'm not receiving mail notifications for changes to this ticket...

Here is the proposed solution for opensuse_welcome issue : https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14575, I am running some VRs and open it for review

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

This bug is still referenced in a failing openQA test: kde_live_upgrade_leap_15.3@64bit
https://openqa.opensuse.org/tests/2285635#step/opensuse_welcome#1/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.

Is the status of this ticket current? any updates? can we resolve the ticket?

@szarate, I am wating for you to upload the cryptlvm qcow2 image and then schedule the upgrade_cryptlvm testsuite. After that, the ticket can be closed.

Thanks @szarate, I just added the new testsuite and scheduled it in Leap runs. It will be visible in the next Build :)

Last upgrade scenario runs fine : https://openqa.opensuse.org/tests/2317436, so I think this ticket can be set as resolved now, wdyt @szarate?