Project

General

Profile

Actions

action #162212

closed

[qe-core] test fails in setup_raid1_lvm

Added by dvenkatachala about 1 month ago. Updated 14 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2024-06-13
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Observation

# Test died: Timed out: 

Not Found
{ "error" : "Widget not found" }

http://10.146.5.91:39132/v1/widgets?action=select&id=%22Y2Partitioner%3A%3AWidgets%3A%3AOverviewTree%22&value=RAID at
sle/lib/YuiRestClient/Http/HttpClient.pm line 33.

openQA test in scenario sle-15-SP4-Online-QR-x86_64-Build195.1-lvm+RAID1@svirt-xen-hvm fails in
setup_raid1_lvm

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: slindomansilla, jrauch

Combination of LVM and RAID1, installation of RAID1 on top of LVM using expert partitioner.

(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.

Reproducible

Fails since (at least) Build 195.1

Expected result

Last good: 192.9 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by dzedro about 1 month ago · Edited

I fixed this just by adding, this was done also for 15-SP5 YAML_TEST_DATA test_data/qam/QR/15-SP4/lvm_raid1/lvm+raid1_svirt-xen.yaml
https://openqa.suse.de/tests/14570409

Actions #2

Updated by dzedro about 1 month ago · Edited

  • File image(1).png added
  • Status changed from New to Rejected
Actions #3

Updated by dzedro about 1 month ago

  • File deleted (image(1).png)
Actions #4

Updated by dzedro about 1 month ago

  • Status changed from Rejected to New
Actions #5

Updated by openqa_review 18 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: lvm+RAID1@svirt-xen-hvm
https://openqa.suse.de/tests/14735264#step/setup_raid1_lvm/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.

Actions #6

Updated by rfan1 15 days ago

  • Assignee set to dzedro

Hi Jozef, can you please take this ticket then?

Actions #7

Updated by dzedro 14 days ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF