Project

General

Profile

action #115916

[security] test fails in version_check

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

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

100%

Estimated time:
Difficulty:
Tags:

Description

SUSEConnect failed activating module PackageHub after 1 retries
The test cannot activate PackageHub in x86_64, s390x, aarch64. Investigate the issue and check if it is a product bug.

Acceptance criteria

  1. Identify if it is a product bug
  2. If it is a bug, open a bugzilla ticket under SUSE Linux Enterprise Server 15 SP5
  3. If it is a test issue, adjust the test accordingly and run Verification runs.

Observation

openQA test in scenario sle-15-SP5-Online-x86_64-security_smartcard_update@64bit fails in
version_check

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

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

History

#1 Updated by punkioudi 3 months ago

  • Status changed from New to In Progress

Acoording to the [bug], PackageHub is not yet setup in SLE 15-SP5, so we cannot yet run this test.
I propose to soft-fail it until PackageHub is available in SLE 15-SP5.

#2 Updated by punkioudi 3 months ago

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

The same issue happens with lynis_setup.pm, where the PackageHub needs to be activated.
I set the ticket in Feedback, until PackageHub is added in 15-SP5 (It is mentioned in PRD confluence page that it will come in Beta milestone).

#3 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: lynis_gnome
https://openqa.suse.de/tests/9417452#step/lynis_setup/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 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: lynis_gnome
https://openqa.suse.de/tests/9680062#step/lynis_setup/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.

Also available in: Atom PDF