Project

General

Profile

Actions

action #61925

closed

[functional][u] test fails in user_defined_snapshot - Timeout because system takes longer to shutdown

Added by SLindoMansilla about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2020-01-08
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

The system is rebooting twice. The second time, it takes longer than expected to shutdown, causing the needle match "grub2" to timeout.

Tasks

  1. Improve the test by sending key 'esc' to close plymouth and show what is happening in the console.
  2. Improve the test with shutdown check or increase the timeout.

Reproducible

  • In scenario sle-15-SP2-Online-x86_64-extra_tests_on_gnome@64bit
  • Fails since Build 120.1

Expected result

Last good: 108.1

Further details

Always latest result in this scenario: latest

Actions #1

Updated by maritawerner about 4 years ago

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

Actions #2

Updated by SLindoMansilla about 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Priority changed from Normal to High
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h
Actions #3

Updated by zluo about 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to zluo

take over

Actions #4

Updated by zluo about 4 years ago

https://openqa.suse.de/tests/3826537 running with my PR now. Check later.

Actions #6

Updated by zluo about 4 years ago

  • Status changed from In Progress to Resolved
Actions #7

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: extra_tests_on_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/3963816

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 #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: extra_tests_on_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4038464

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

Also available in: Atom PDF