Project

General

Profile

Actions
Copy link

action #105609

closed

[sle][security][sle15sp4][powervm]test fails in boot_to_desktop

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

Status:
Resolved
Priority:
High
Assignee:
rfan1
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-01-27
Due date:
% Done:

100%

Estimated time:
2.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-Online-ppc64le-security_smartcard_update@ppc64le-hmc-single-disk fails in
boot_to_desktop

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 88.4 (current job)

Expected result

Last good: 88.4 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by rfan1 over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 40
  • Estimated time set to 2.00 h

Thanks to @llzhao for the reminder

There is some problem with job setting:

I have fixed already, let us see next openQA run

@@ -205,7 +205,7 @@
         testsuite: null
         settings:
           BOOT_HDD_IMAGE: '1'
-          START_AFTER_TEST: create_hdd_textmode_hmc
+          START_DIRECTLY_AFTER_TEST: create_hdd_textmode_hmc
           HDD_1: '%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2'
           YAML_SCHEDULE: schedule/security/smartcard.yaml
           DESKTOP: textmode
Actions
Copy link
 #2

Updated by rfan1 over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 40 to 100
Actions
Copy link
 #3

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: security_smartcard_update
https://openqa.suse.de/tests/8426469#step/boot_to_desktop/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 44 days if nothing changes in this ticket.

Actions
Copy link

Also available in: Atom PDF