Project

General

Profile

action #115823

[security][fips][refinement] test fails in test_repo_setup

Added by punkioudi 3 months ago. Updated about 1 month ago.

Status:
Feedback
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 --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

  1. Investigate why the repo is not yet added (in the comments of the code it is mentioned that this repo usually comes in delay)
  2. 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

History

#1 Updated by openqa_review 3 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_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:

  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.

#2 Updated by punkioudi 3 months ago

  • Status changed from New to In Progress
  • Assignee set to punkioudi

#3 Updated by punkioudi 2 months 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.

#4 Updated by openqa_review about 2 months 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:

  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.

#5 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_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:

  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