action #115811
closed
[security][fips] test fails in lynx_https
Added by punkioudi over 1 year ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
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
- Investigate the issue if the package belongs to another module, which needs to be activated.
- 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
- 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.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
- Status changed from Blocked to Resolved
- % Done changed from 0 to 100
Tested manually and PackageHub module is activated.
- Related to action #134003: [security][15-SP6][PackageHub] tests fail in links_https and lynx_https because the packages are not found added
Also available in: Atom
PDF