Project

General

Profile

action #116281

[security][fips] test fails in boot_encrypt

Added by punkioudi 3 months ago. Updated 11 days ago.

Status:
Blocked
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-09-06
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:

Description

Observation

# wait_serial expected: "Please enter passphrase for disk.*"
# Result:
  version 2.06


 [?25h   Minimal BASH-like line editing is supported. For the first word, TAB   

   lists possible command completions. Anywhere else TAB lists possible   

   device or file completions.                                            



grub> 

grub>

# Test died: Could not find "enter passphrase" prompt at sle/lib/utils.pm

Same test passes in yast. This is scheduled for the first time under fips, so it needs to be checked.

openQA test in scenario sle-15-SP5-Online-s390x-fips_install_lvm_encrypt_separate_boot@s390x-kvm-sle12 fails in
boot_encrypt

Test suite description

maintainer: richard.fan@suse.com
copy the case from yast team to test with FIPS mode

Reproducible

Fails since (at least) Build 15.2

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #120249: [security][15sp4][QU1] test fails in boot_encrypt on s390xNew2022-11-10

History

#1 Updated by openqa_review 2 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/9516721#step/boot_encrypt/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.

#2 Updated by openqa_review about 2 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/9563449#step/bootloader_start/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.

#3 Updated by amanzini about 1 month ago

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

#4 Updated by amanzini about 1 month ago

  • Status changed from In Progress to Blocked

#5 Updated by openqa_review 25 days 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/9823623#step/boot_encrypt/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.

#6 Updated by amanzini 16 days ago

  • Related to action #120249: [security][15sp4][QU1] test fails in boot_encrypt on s390x added

#7 Updated by openqa_review 11 days 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/9961180#step/boot_encrypt/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.

Also available in: Atom PDF