Project

General

Profile

Actions

action #137018

closed

[security][15-SP6] test fails in install_SLES

Added by pstivanin 7 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-09-26
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:

Description

Observation

openQA test in scenario sle-15-SP6-Online-aarch64-fips_install_encrypt_lvm_separate_boot@aarch64 fails in
install_SLES

fails also on x86_64: https://openqa.suse.de/tests/12203708#step/install_SLES/2
and s390x: https://openqa.suse.de/tests/12203709

Test suite description

Testsuite maintained at https://gitlab.suse.de/qe-security/osd-sle15-security.

Reproducible

Fails since (at least) Build 9.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by pstivanin 7 months ago

  • Subject changed from [security] test fails in install_SLES to [security][15-SP6] test fails in install_SLES
Actions #2

Updated by emiler 7 months ago

  • Status changed from New to Feedback

The issue is that SP6 is a beta distribution, which requires an extra step during installation. The solution is a conditional schedule. We should avoid this in the future by migrating to autoyast, which is currently being worked on.

PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17867

Actions #3

Updated by emiler 7 months ago

  • Status changed from Feedback to Resolved

Merged, closing.

Actions #4

Updated by openqa_review 7 months 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: fips_install_encrypt_lvm_separate_boot
https://openqa.suse.de/tests/12203709#step/accept_license/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 #5

Updated by emiler 7 months ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF