Project

General

Profile

action #124931

[security][QU] 15-SP4 fips_install_lvm_encrypt_seprate_boot test fails in first_boot

Added by tjyrinki_suse 3 months ago. Updated about 2 months ago.

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

100%

Estimated time:
Difficulty:
Tags:
fail

Description

Observation

openQA test in scenario sle-15-SP4-Online-QR-x86_64-fips_install_lvm_encrypt_separate_boot@64bit fails in
first_boot (Always latest result in this scenario: latest) Last good: 171.2 (or more recent)

This is likely due to the changes by YaM (YaST) team.

Related issues

Related to openQA Tests - action #113162: [security][FIPS][15-SP4][15-SP5] Implement & Integrate LUKS test case into openQA Resolved2022-03-29

History

#1 Updated by tjyrinki_suse 3 months ago

  • Related to action #113162: [security][FIPS][15-SP4][15-SP5] Implement & Integrate LUKS test case into openQA added

#2 Updated by emiler 3 months ago

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

This happens because the test expects GDM login screen instead of a shell. A fix would be to set DESKTOP=textmode in the test suite, but this will be fixed by my new implementation of fips encryption schedules, see https://progress.opensuse.org/issues/113162.

#3 Updated by openqa_review 3 months ago

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_lvm_encrypt_separate_boot
https://openqa.suse.de/tests/10605119#step/first_boot/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.

#4 Updated by emiler 3 months ago

I've tested a run with the mentioned solution and it passes: http://emiler-openqa.qe.suse.de/tests/156

#5 Updated by emiler 3 months ago

  • % Done changed from 0 to 100

#6 Updated by emiler 3 months ago

  • % Done changed from 100 to 0

#7 Updated by emiler 3 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

PRs above have been merged and test runs pass. I am going to close this, but keep an eye open for the next full QU run.

#8 Updated by openqa_review 2 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_lvm_encrypt_separate_boot
https://openqa.suse.de/tests/10605119#step/first_boot/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.

#9 Updated by tjyrinki_suse about 2 months ago

  • Status changed from Feedback to Resolved

Erronous reopening, a month old reference.

Also available in: Atom PDF