action #102236
open[qe-core] test fails in system_prepare - change of permissions fails
0%
Description
Observation¶
notes¶
Also switch the test to use serial terminal
openQA test in scenario sle-15-SP4-Online-x86_64-default@svirt-hyperv fails in
system_prepare
Test suite description¶
Maintainer: QE Core
The standard scenario where we mainly just follow installation suggestions without any adjustments.
Reproducible¶
Fails since (at least) Build 55.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by openqa_review over 2 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/7716784
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 2 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/7805942
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by tjyrinki_suse over 2 years ago
- Status changed from New to Workable
- Target version set to Ready
- Start date deleted (
2021-11-10)
Updated by apappas over 2 years ago
- Status changed from Workable to In Progress
- Assignee set to apappas
From what I can tell this is failing because the SUT is a hyperv guest doesn't have a serial console ( the SERIAL_CONSOLE is 0). Is the proposed remedy to check before switching to serial console?
Updated by szarate over 2 years ago
No, the test is failing because for some reason the serial commands are not surviving for some reason?...
perhaps you could try running the test up to the grub test part, connect via VNC to the SUT and check that these persist... as they do for other arches. Maybe @mloviska knows a thing or two too...
You're right with the serial console part, did not occurr to me when I created the ticket, however, select_serial_console should be able to select root console if there's no serial console support
Updated by openqa_review over 2 years ago
- Due date set to 2021-12-28
Setting due date based on mean cycle time of SUSE QE Tools
Updated by okurz over 2 years ago
- Target version changed from Ready to QE-Core: Ready
@tjyrinki_suse I assume you intended to use the target version "QE-Core: Ready"
Updated by openqa_review over 2 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/7924236
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by JERiveraMoya over 2 years ago
- Related to action #97745: [virtualization][hyperv] ensure_serialdev_permissions fails for hyperv added
Updated by JERiveraMoya over 2 years ago
In latest build we changed (accidentally) to previous version of hyperv and got worse, so we revert to the new one. With the new one in YaST group we have scenarios constantly failing. I linked the related ticket.
Updated by apappas over 2 years ago
- Status changed from In Progress to Blocked
I am setting this to blocked since, as mentioned in the related ticket and in discussions in slack, this is an issue with the way the hypervisor behaves and what os-autoinst expects than a test issue.
Updated by okurz over 2 years ago
This ticket had a due set but exceeded it already by more than 14 days. We would like to take the due date seriously so please update the ticket accordingly (resolve the ticket or update the due-date or remove the due-date). See https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives for details. As this is a blocked ticket waiting for IIUC #97745 I suggest to remove the due-date or set a feasible value a bit further in the future until when you want to escalate the problem in the blocking issue.
Updated by szarate about 2 years ago
- Assignee changed from apappas to szarate
this needs to be looked at and serial dev permissions needs to be moved to an udev rule added by the first boot module or a new module that prepares the sut for openQA testing (There are other tickets in the backlog related to this)
Updated by openqa_review almost 2 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/8752634#step/system_prepare/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 192 days if nothing changes in this ticket.
Updated by openqa_review over 1 year 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-uefi
https://openqa.suse.de/tests/10219966#step/system_prepare/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 384 days if nothing changes in this ticket.
Updated by slo-gin about 1 month ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.