Project

General

Profile

Actions
Copy link

action #152897

open

[security][qu] SCC_REGCODE_LIVE not defined in QU test runs (and test fails in suseconnect)

Added by tjyrinki_suse 4 months ago. Updated 2 months ago.

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

0%

Estimated time:
4.00 h
Difficulty:
Tags:
fail, qu

Description

openQA test in scenario sle-15-SP5-Online-QR-x86_64-fips_ker_mode_tests_crypt_tool@64bit fails in
suseconnect

The new suseconnect test module needs SCC_REGCODE_LIVE, but for some reason this is not defined in QU. This is likely to be fixed in medium types settings.

The variable is included in 15-SP6 (https://openqa.suse.de/tests/13085715#) and maintenance (https://openqa.suse.de/tests/13134299#), and in those cases the module passes.

Actions
Copy link
 #1

Updated by tjyrinki_suse 4 months ago

  • Description updated (diff)
  • Estimated time changed from 8.00 h to 4.00 h
Actions
Copy link
 #2

Updated by tjyrinki_suse 4 months ago

  • Status changed from Workable to In Progress
  • Assignee set to tjyrinki_suse
Actions
Copy link
 #3

Updated by tjyrinki_suse 4 months ago

  • Status changed from In Progress to Resolved

Added SCC_REGCODE_LIVE for x86 and s390x. Not found for aarch64, so if you find this ticket via future aarch64 run, you can consider filing another ticket for it... it's not being executed in maintenance: aggregate updates for aarch64.

Verification run: https://openqa.suse.de/tests/13137012#details

Actions
Copy link
 #4

Updated by openqa_review 4 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_ker_mode_tests_crypt_tool
https://openqa.suse.de/tests/13123875#step/suseconnect/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
Copy link
 #5

Updated by tjyrinki_suse 4 months ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #6

Updated by openqa_review 3 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_ker_mode_tests_crypt_tool
https://openqa.suse.de/tests/13214906#step/suseconnect/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
Copy link
 #7

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_ker_mode_tests_crypt_tool
https://openqa.suse.de/tests/13311972#step/suseconnect/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 56 days if nothing changes in this ticket.

Actions
Copy link

Also available in: Atom PDF