Project

General

Profile

action #94264

[migration] test fails in boot_to_desktop in mru multipath tests all the times

Added by mgrifalconi 6 months ago. Updated about 19 hours ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP3-Server-DVD-Updates-x86_64-mru-install-multipath-remote@64bit fails in
boot_to_desktop

Test suite description

NETWORK_INIT_PARAM=ifcfg=eth0=dhcp4 to skip dhcp-question which isproblematic on 12sp1

Reproducible

Fails since (at least) Build 20210618-2 (current job)

Expected result

Last good: 20210617-1 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by openqa_review 5 months ago

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

This bug is still referenced in a failing openQA test: mru-install-multipath-remote
https://openqa.suse.de/tests/6392904

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 label in the openQA scenario is removed

#2 Updated by tjyrinki_suse 4 months ago

  • Status changed from New to Workable
  • Start date deleted (2021-06-18)

#3 Updated by tjyrinki_suse 4 months ago

This is "Workable" only in the sense that it'd need to be studied what is causing these problems, there is no one clear reason for the failures.

#4 Updated by openqa_review 3 months ago

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

This bug is still referenced in a failing openQA test: mru-install-multipath-remote
https://openqa.suse.de/tests/7020193

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 label in the openQA scenario is removed

#5 Updated by szarate 3 months ago

I think it's a bug, https://openqa.suse.de/tests/7020193#step/boot_to_desktop/7 7 minutes it's a long long time.

#6 Updated by openqa_review 2 months ago

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

This bug is still referenced in a failing openQA test: mru-install-multipath-remote
https://openqa.suse.de/tests/7174233

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

#7 Updated by tjyrinki_suse 2 months ago

  • Project changed from openQA Tests to qe-yast
  • Subject changed from [qe-core] test fails in boot_to_desktop around 50% of times to [qe-yast] test fails in boot_to_desktop around 50% of times
  • Category deleted (Bugs in existing tests)
  • Status changed from Workable to New

Moving to QE Yast as now it has been seen it happens in multipath cases every time:

https://openqa.suse.de/tests/7174233#next_previous

Putting to new as should be triaged to Workable by PO.

#8 Updated by oorlov about 2 months ago

Timo, why do you think it is related to YaST? Could you please share a link to the continuous failure, as you last link leads to 404.

#9 Updated by mgrifalconi about 2 months ago

oorlov here is one example of sporadic failure still happening https://openqa.suse.de/tests/7307038#next_previous

#10 Updated by openqa_review 24 days ago

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

This bug is still referenced in a failing openQA test: mru-install-multipath-remote
https://openqa.suse.de/tests/7624827

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

#11 Updated by oorlov 22 days ago

  • Project changed from qe-yast to openQA Tests
  • Subject changed from [qe-yast] test fails in boot_to_desktop around 50% of times to test fails in boot_to_desktop around 50% of times

IMHO, it is not related to YaST. It happens on boot.

If any assistance from QE YaST team is required, we are happy to help, but we did not create this test suite and don't have expertise in this area.

#12 Updated by okurz 22 days ago

  • Category set to Bugs in existing tests

#13 Updated by maritawerner 16 days ago

I have no idea whom to assign that ticket. It seems that it is moving back and forth from qe-core and qe-yast?

#14 Updated by tjyrinki_suse 8 days ago

  • Subject changed from test fails in boot_to_desktop around 50% of times to [migration] test fails in boot_to_desktop in mru multipath tests around 50% of times

multipath test modules and testing are maintained by QE Yast as such, but these mru*multipath test suites are another former maintenance department developed test suites.

The failing module however boot_to_desktop has Maintainer: yuwang@suse.com who is in QE Migration, maybe she can help to at least understand the topic? I mean it doesn't really matter whose this ticket should be as such, but we should find people who understand what is going on with it and how it eg differs to other multipath using tests which do not have the same failure.

#15 Updated by mgrifalconi 7 days ago

  • Priority changed from Normal to High

Increasing prio since it is happening very often and blocking updates

#16 Updated by coolo 5 days ago

  • Subject changed from [migration] test fails in boot_to_desktop in mru multipath tests around 50% of times to [migration] test fails in boot_to_desktop in mru multipath tests all the times

Fixing the subject

Also available in: Atom PDF