QA » openQA Project

take over and check

PR merged.

set is as resolved now.

Hi, this can't be resolved as long as there are soft-failure references to this ticket https://openqa.suse.de/tests/10375315#step/bootloader/25 so please make sure the according test code does not reference this or any other ticket in a soft-fail.

Hello, don't see the reason to keep this ticket in feedback.

The record_softfailure will reopen the ticket automatically as Oliver said.
To resolve the ticket we should remove the softfailure mark in the code and just retry on failures or invest more on the problem and actually solve it.

There is no chance to fix from our side, this is clearly an issue on qanet and network issue.

@okurz

the root cause is on qanet and network issue happened sporadic. With my previous workaround(re-try, reset) it cannot be fixed.
So please help to fix the issue. I can remove softfail of course, then we go back to the problem as we had before.

zluo wrote:

https://progress.opensuse.org/issues/120570 this looks not good and it seems to be an new issue with network.

1. You are just referencing this ticket itself. Did you want to include another reference?

zluo wrote:

@okurz

the root cause is on qanet and network issue happened sporadic. With my previous workaround(re-try, reset) it cannot be fixed.
So please help to fix the issue. I can remove softfail of course, then we go back to the problem as we had before.

1. Could you please share a bit more context what you think the issue is?

Following the openQA test URL from #120570-19 in "Next & Previous" I find as latest job in this scenario failing with the same error symptoms
https://openqa.suse.de/tests/11162717
In https://openqa.suse.de/tests/11162717#step/bootloader/25 I can see the job loading initrd from the file path "mnt/openqa/repo/SLE-15-SP5-Online-ppc64le-Build102.1-Media1/boot/ppc64le/initrd. That's a path on qanet relative to /srv/tftp . The file /srv/tftp/mnt/openqa/repo/SLE-15-SP5-Online-ppc64le-Build102.1-Media1/boot/ppc64le/initrd exists and it is there right now. It's an "XZ compressed data" so I am pretty sure it is intact and it could be read in grub, otherwise grub would have reported a timeout reading or something. Also https://openqa.suse.de/tests/11176137#step/bootloader/25 on the same machine grenache-1:22 "redcurrant-2" passed and had no problems reading the same file

1. How to reproduce?

2. To keep the overview I suggest you update the ticket description according to the template https://progress.opensuse.org/projects/openqav3/wiki/#Further-decision-steps-working-on-test-issues and follow https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation to better understand the statistics

3. For further investigation I suggest to only schedule tests with the test module "bootloader" and with video enabled

reducing prio as there is apparently less interest from reporter.

I assume the problem resolved itself because unfortunately there is no further response. I checked if there are any recent job labels using this ticket but openqa-query-for-job-label 120570 shows that we are good:

11162717|2023-05-19 15:17:50|done|failed|textmode+role_textmode||grenache-1
11146733|2023-05-17 03:26:25|done|failed|textmode+role_textmode||grenache-1
11140430|2023-05-16 15:01:14|done|failed|textmode+role_textmode||grenache-1

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

This bug is still referenced in a failing openQA test: textmode+role_textmode@ppc64le-hmc
https://openqa.suse.de/tests/11162717#step/bootloader/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.

reminded rfan1 about the SLE15-SP6 setup in #131531 which is relevant here. That might be enough.