Project

General

Profile

action #115811

[security][fips] test fails in lynx_https

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

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

100%

Estimated time:
Difficulty:
Tags:

Description

# Test died: 'zypper -n --no-refresh --no-gpg-checks in lynx' failed with code 104
No provider of lynx found

Is lynx package located probably to a module that is not activated or is it forgotten?

##Acceptance Criteria

  1. Investigate the issue if the package belongs to another module, which needs to be activated.
  2. If it is a product bug, open one under SLE Server 15 SP5

Observation

openQA test in scenario sle-15-SP5-Online-x86_64-fips_env_mode_tests_crypt_web@64bit fails in
lynx_https

Test suite description

Maintainer: bchou@suse.com. Workaround for FIPS single module 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

History

#1 Updated by punkioudi 3 months ago

  • Status changed from New to Blocked
  • Assignee set to punkioudi

PackageHub is not yet activated in 15-SP5 and this package used to be in this module, so we can soft-fail it for now.

#2 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_env_mode_tests_crypt_web
https://openqa.suse.de/tests/9517905#step/links_https/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 openqa_review about 1 month 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_env_mode_tests_crypt_web
https://openqa.suse.de/tests/9680031#step/links_https/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.

#4 Updated by punkioudi 3 days ago

  • Status changed from Blocked to Resolved
  • % Done changed from 0 to 100

Tested manually and PackageHub module is activated.

Also available in: Atom PDF