action #115823
closed[security][fips][refinement] test fails in test_repo_setup
100%
Description
# Test died: 'zypper -n --gpg-auto-import-keys refresh' failed with code 4
Related zypper logs:
2022-08-24 11:25:46 <5> susetest(3529) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):804 THROW: File '/repodata/repomd.xml' not found on medium 'http://download.nvidia.com/suse/sle15sp5'
2022-08-24 11:25:46 <5> susetest(3529) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):804 THROW: File '/content' not found on medium 'http://download.nvidia.com/suse/sle15sp5'
It seems that in https://download.nvidia.com/suse/ the repo for 15-SP5 is not there yet.
Suggestions¶
- Investigate why the repo is not yet added (in the comments of the code it is mentioned that this repo usually comes in delay)
- Workaround/Skip this step for the early phases of product development
Observation¶
openQA test in scenario sle-15-SP5-Online-x86_64-fips_env_mode_tests_crypt_x11@64bit fails in
test_repo_setup
Test suite description¶
Maintainer: bchou@suse.com
Reproducible¶
Fails since (at least) Build 15.2 (current job)
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by openqa_review over 1 year 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_x11
https://openqa.suse.de/tests/9418315#step/test_repo_setup/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.
Updated by punkioudi over 1 year ago
- Status changed from New to In Progress
- Assignee set to punkioudi
Updated by punkioudi over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Nvidia repo will be available in the next milestones, so this issue can be ignored for now.
Updated by openqa_review over 1 year 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_env_mode_tests_crypt_x11
https://openqa.suse.de/tests/9565385#step/test_repo_setup/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.
Updated by openqa_review over 1 year 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_x11
https://openqa.suse.de/tests/9759728#step/test_repo_setup/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.
Updated by punkioudi about 1 year ago
- Status changed from Feedback to Resolved
Issue doesn't appear anymore.