Project

General

Profile

Actions

action #97013

closed

[qe-core][qe-yast] test fails in handle_reboot, patch_and_reboot, installation

Added by mgrifalconi over 3 years ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-08-17
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

There are a lot of different tests that hangs on boot. Unclear if YaST has something to do with it, some joint check between YaST and qe-core may help.

Few other random examples:
https://openqa.suse.de/tests/6899580
https://openqa.suse.de/tests/6900469

hypfs.7f5705: The hardware system does not support hypfs

hypfs.7a79f0: Initialization of hypfs failed with rc=-61

dracut-pre-pivot[316]: Warning: No /usr/bin/grub2-emu in /sysroot--dropping to emergency shell...
dracut-pre-pivot[316]: Warning:

Give root password for maintenance
(or press Control-D to continue): 

openQA test in scenario sle-12-SP5-Server-DVD-Updates-s390x-qam-gnome@s390x-kvm-sle15 fails in
handle_reboot

Test suite description

Reproducible

Fails since (at least) Build 20210817-1

Expected result

Last good: 20210816-1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (1 open0 closed)

Related to openQA Tests (public) - action #95458: [qe-sap][ha] SUT reboots unexpectedly, leading to tests failing in HA scenarios auto_review:"(?s)tests/ha.*(command.*timed out|Test died).*match=root-console timed out":retryFeedbackacarvajal2021-07-13

Actions
Actions #1

Updated by mgrifalconi over 3 years ago

  • Subject changed from [qe-core] test fails in handle_reboot to [qe-core] test fails in handle_reboot, patch_and_reboot, installation
Actions #2

Updated by punkioudi over 3 years ago

Imo, it can be also tagged as a qe-yast ticket (:

Actions #3

Updated by mgrifalconi over 3 years ago

  • Subject changed from [qe-core] test fails in handle_reboot, patch_and_reboot, installation to [yast] test fails in handle_reboot, patch_and_reboot, installation
Actions #5

Updated by mgrifalconi over 3 years ago

  • Subject changed from [yast] test fails in handle_reboot, patch_and_reboot, installation to [qe-core][yast] test fails in handle_reboot, patch_and_reboot, installation
  • Description updated (diff)
  • Priority changed from Normal to Urgent
Actions #6

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [qe-core][yast] test fails in handle_reboot, patch_and_reboot, installation to [qe-core][qe-yast] test fails in handle_reboot, patch_and_reboot, installation
Actions #7

Updated by szarate over 3 years ago

  • Related to action #95458: [qe-sap][ha] SUT reboots unexpectedly, leading to tests failing in HA scenarios auto_review:"(?s)tests/ha.*(command.*timed out|Test died).*match=root-console timed out":retry added
Actions #8

Updated by okurz over 3 years ago

  • Priority changed from Urgent to Normal

Discussed in weekly QE sync together. This ticket showed up violating the SLO for urgent tickets. We agreed that the ticket is actually not urgent according to these criteria. See https://progress.opensuse.org/projects/openqatests/wiki#SLOs-service-level-objectives for details

Actions #9

Updated by oorlov about 3 years ago

I guess this is not something that QE YaST team can help with. YaST is a tool for administering and maintaining a SUSE Linux installation. Here it fails on boot, so it is something different.

Anyways, if any assistance from QE YaST team is required, we are happy to help.

Actions #10

Updated by slo-gin about 2 years 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.

Actions #11

Updated by slo-gin 9 months 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.

Actions #12

Updated by mgrifalconi 9 months ago

  • Status changed from New to Resolved

Related bug was fixed

Actions

Also available in: Atom PDF