Project

General

Profile

Actions
Copy link

action #122146

closed

Investigate bsc#1206013 with svirt-xen-pv not able to use graphical since SLE 15 SP5 (build 52.4)

Added by syrianidou_sofia over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
JRivrain
Target version:
-
Start date:
2022-12-19
Due date:
% Done:

0%

Estimated time:

Description

For Product validation SLE 15 SP5, al openQA job running svirt-xen-pv cannot run in graphical mode since build 52.4.
With previous builds still works.
Several things were tested in this bug but QE Virtualization expertice will be needed to continue figuring out what it is the root cause as the bug was marked as invalid.
https://bugzilla.suse.com/show_bug.cgi?id=1206013

Related issues 1 (0 open — 1 closed)

Related to qe-yam - action #122167: Move all svirt-xen-pv scenarios booting in graphical mode to Develpmet job groupResolvedhjluo2022-12-19

Actions
Actions
Copy link
 #1

Updated by syrianidou_sofia over 2 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #2

Updated by JERiveraMoya over 2 years ago

  • Project changed from qe-yam to 204
  • Description updated (diff)
Actions
Copy link
 #3

Updated by JERiveraMoya over 2 years ago

  • Subject changed from Collect more data for bug#1206013 to Investigate bsc#1206013 with svirt-xen-pv not able to use graphical since SLE 15 SP5 (build 52.4)
Actions
Copy link
 #4

Updated by JERiveraMoya over 2 years ago

  • Project changed from 204 to qe-yam
  • Priority changed from High to Normal
Actions
Copy link
 #5

Updated by JERiveraMoya over 2 years ago

  • Project changed from qe-yam to 204
Actions
Copy link
 #6

Updated by JERiveraMoya over 2 years ago

  • Related to action #122167: Move all svirt-xen-pv scenarios booting in graphical mode to Develpmet job group added
Actions
Copy link
 #7

Updated by xlai over 2 years ago

  • Status changed from New to In Progress
  • Assignee set to xlai

I give my analysis, trying results and logs in https://bugzilla.suse.com/show_bug.cgi?id=1206013#c36. I am afraid that's all I can help.

Next step, I would suggest to change the bug's component to either XEN or X to let developer experts of each component to further check.

Actions
Copy link
 #8

Updated by xlai over 2 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from xlai to JRivrain
Actions
Copy link
 #9

Updated by JRivrain over 2 years ago

  • Status changed from Feedback to Resolved

Thanks, bug reopened.

Actions
Copy link
 #10

Updated by openqa_review over 2 years ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: minimal+base_yast@svirt-xen-pv
https://openqa.suse.de/tests/10220489#step/setup_libyui/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
Copy link
 #11

Updated by JRivrain over 2 years ago

  • Project changed from 204 to qe-yam
  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF