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.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
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.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Priority changed from Normal to High
This Testcase fails twice in osd. Could we get that fixed until beta2 in two weeks?
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- 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.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Status changed from Workable to Rejected
- Assignee set to zluo
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Also available in: Atom
PDF