Comment # 7 on bug 1162320 from Oliver Kurz

If you really think https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c6 is
the right solution which I would find very bad as users can unknowingly run
into unbootable systems then please at least update this and other other bug
accordingly to communicate this intention. This bug here is still in "NEW" and
you are the bug assignee but I guess it should be in "CONFIRMED" or
"IN_PROGRESS" with an update on the actual plan, right? Or even set it to
"RESOLVED" with the according resolution, e.g. pointing to the release notes
that cover this for Leap and other distributions.

I just checked again on the machine "aarch64" and just upgrading the package
grub2-arm64-efi still breaks the boot with the same error as originally
reported. Please keep in mind that this bug here is about an upgrade on a
physical machine, so neither "migration" between different versions of products
nor an openQA test itself.

Also, the workaround as mentioned in
https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c28 did not work for me.
I assume that the instructions are incomplete, e.g. if the btrfs subvolume
needs to be mounted or so. There is also an unanswered question about this in
https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c34

> Admittedly I am not much into openQA, but sourcing from bsc#1097235 claimed that the problem has been fixed, why openQA still (constantly) notify the failure result ? Is there anything from the test case has to check for a more close result ?

Regarding openQA test failure reminders, as
https://bugzilla.opensuse.org/show_bug.cgi?id=1122591#c49 states:

> This bug is still referenced in a failing openQA test: 
> migration_media+scc_sle15_ha_alpha_node01
> https://openqa.suse.de/tests/3886491
>
> 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"
> 3. The label in the openQA scenario is removed

https://openqa.suse.de/tests/3886491#step/patch_sle/106 is the location in test
results which seems to record the soft failure which comes from
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/2e020725b70964a3465730411694e2849b3d487a/lib/utils.pm#L1583
after checking that the necessary btrfs subvolume is not already there. So I
consider the products still affected because either the bugfix is not effective
or never reached the affected product(s).