Project

General

Profile

action #94723

[qe-yast][qe-core][qem] test fails in installation due to SCC key rotation

Added by mgrifalconi almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-06-25
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Server-DVD-Updates-x86_64-qam-allpatterns@64bit fails in
installation

Test suite description

Default system config with all patterns enabled.
Due changes in autoyast profile size of HDD incerased to 40GB

Reproducible

Fails since (at least) Build 20210625-1

Expected result

Last good: 20210624-1 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by okurz almost 2 years ago

Called openqa-label-all --openqa-host https://openqa.suse.de --label '* installation: https://progress.opensuse.org/issues/94723' --module installation

#2 Updated by szarate almost 2 years ago

Ideas

  • CI checks to avoid regcodes being published (There's a github checker for this, we just need to enable it and use it in the github actions.)
  • One central place to have the SCC regcodes, that is used by the tests/openQA (so there's only one place to change)
  • openQA api search by key/value

#3 Updated by okurz almost 2 years ago

szarate wrote:

Ideas

  • CI checks to avoid regcodes being published (There's a github checker for this, we just need to enable it and use it in the github actions.)

But you can't prevent people commiting something and pushing that information. CI-checks only run after that. Or do you mean something like a pre-commit hook that would be executed locally?

  • One central place to have the SCC regcodes, that is used by the tests/openQA (so there's only one place to change)

That's a good idea. I see that part of the saga #58184. We currently stopped working on that saga as we are asked to focus on #91646

#4 Updated by oorlov almost 2 years ago

  • Status changed from New to Closed

Test is not failing anymore. So, closing.

Also available in: Atom PDF