Project

General

Profile

Actions
Copy link

action #58790

closed

[functional][u][virtualization] test fails in bootloader_svirt: Too many attempts to format HDD

Added by dheidler over 4 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
High
Assignee:
zluo
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2019-10-29
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Installer-DVD-x86_64-memtest@svirt-xen-hvm fails in
bootloader_svirt

Suggestions

  • Create a CRON/timer to remove the assets.

Reproducible

Fails since (at least) Build 72.1 (current job)

Expected result

Last good: 67.1 (or more recent)

Further details

Always latest result in this scenario: latest

# Test died: {
  'function' => 'add_disk',
  'args' => [
              {
                'dev_id' => 'b',
                'create' => 1,
                'size' => '20G'
              }
            ],
  'json_cmd_token' => 'KSKYECKe',
  'cmd' => 'backend_proxy_console_call',
  'console' => 'svirt'
}
Too many attempts to format HDD at /usr/lib/os-autoinst/consoles/sshVirtsh.pm line 362.
Actions
Copy link
 #1

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: create_hdd_gnome@svirt-xen-pv
https://openqa.suse.de/tests/3591711

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
Actions
Copy link
 #2

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: create_hdd_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/3641533

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
Actions
Copy link
 #3

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: create_hdd_gnome@svirt-xen-pv
https://openqa.suse.de/tests/3699709

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
Actions
Copy link
 #4

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: allpatterns@svirt-xen-hvm
https://openqa.suse.de/tests/3736119

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
Actions
Copy link
 #5

Updated by okurz about 4 years ago

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

This bug is still referenced in a failing openQA test: allpatterns@svirt-xen-pv
https://openqa.suse.de/tests/3796770

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
Actions
Copy link
 #6

Updated by maritawerner about 4 years ago

  • Priority changed from Normal to High

This Testcase fails twice in osd. Could we get that fixed until beta2 in two weeks?

Actions
Copy link
 #7

Updated by SLindoMansilla about 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h
Actions
Copy link
 #8

Updated by okurz about 4 years ago

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

This bug is still referenced in a failing openQA test: create_hdd_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/3938965

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
Actions
Copy link
 #9

Updated by okurz about 4 years ago

  • Subject changed from [functional][u] test fails in bootloader_svirt: Too many attempts to format HDD to [functional][u][virtualization] test fails in bootloader_svirt: Too many attempts to format HDD

Please ask [virtualization] for help.

Actions
Copy link
 #10

Updated by okurz about 4 years ago

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

This bug is still referenced in a failing openQA test: default@svirt-hyperv
https://openqa.suse.de/tests/4016309

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
Actions
Copy link
 #11

Updated by okurz about 4 years ago

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

This bug is still referenced in a failing openQA test: default@svirt-hyperv
https://openqa.suse.de/tests/4080931

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
Actions
Copy link
 #12

Updated by zluo about 4 years ago

https://openqa.suse.de/tests/4080933#next_previous shows that we don't have this issue for a long time.

Actions
Copy link
 #13

Updated by zluo about 4 years ago

  • Status changed from Workable to Rejected
  • Assignee set to zluo

https://openqa.suse.de/tests/4093804 shows also okay, the comment #11 mentioned is different issue which doesn't happen at moment.

Actions
Copy link
 #14

Updated by okurz almost 4 years ago

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

This bug is still referenced in a failing openQA test: default@svirt-hyperv
https://openqa.suse.de/tests/4146561

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
Actions
Copy link
 #15

Updated by okurz almost 4 years ago

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

This bug is still referenced in a failing openQA test: default@svirt-hyperv
https://openqa.suse.de/tests/4200702

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
Actions
Copy link

Also available in: Atom PDF