Project

General

Profile

Actions
Copy link

action #134990

closed

Sporadic failure in zypper_migration due to invalid repo URL

Added by syrianidou_sofia over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
tinawang123
Target version:
Current
Start date:
2023-09-01
Due date:
% Done:

0%

Estimated time:

Description

Two migration tests fail due to invalid SP6 repositories:
ppc64le test in migration misc. : https://openqa.suse.de/tests/11954086#step/scc_registration/4
x86_64 test in migration daily : https://openqa.suse.de/tests/11961594/modules/zypper_migration/steps/9

In zypper log :

2023-08-31 05:08:25 susetest(11062) [zypp-core] Exception.cc(log):186 repos.cc(build_cache):456 CAUGHT: [SUSE_Linux_Enterprise_Server_15_SP6_x86_64:SLE-Product-SLES15-SP6-Pool|https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP6/x86_64/product?-GSt7JnzfNnwwVlBHE1U_FghhBtzPI_3FTYvrOITzaBHvIVp2JHNJHsUkAIpTFvr6Zt7gAZb-SnBLueKEIKhaITo8VGa9_fSJlJOVbrVdGLtKZbAQSrfPMGlByEZMPUxS7378F3AHPEhvwdZ5Maq3eQ5og] Valid metadata not found at specified URL

Observation

openQA test in scenario sle-15-SP6-Migration-from-SLE15-SPx-x86_64-online_sles15sp3_ltss_pscc_basesys-srv-def_minimal_zypp@64bit fails in
zypper_migration

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 16.1

Expected result

Last good: 13.4 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by syrianidou_sofia over 1 year ago

  • Project changed from openQA Tests (public) to qe-yam
  • Category deleted (Bugs in existing tests)
  • Target version set to Current
Actions
Copy link
 #2

Updated by syrianidou_sofia over 1 year ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by zoecao over 1 year ago

For the online migration case in daily group, adding setting SCC_PROXY_URL=http://all-%BUILD%.proxy.scc.suse.de could resolve the issue.

Actions
Copy link
 #4

Updated by tinawang123 about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to tinawang123
Actions
Copy link
 #6

Updated by tinawang123 about 1 year ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #7

Updated by openqa_review about 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: offline_sle12sp4_sles12sp5_sles15sp5_pscc_all_full_
https://openqa.suse.de/tests/12120806#step/scc_registration/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.

Actions
Copy link
 #8

Updated by tinawang123 about 1 year ago

  • Status changed from Feedback to Resolved

As image name changed, update the settings.

Actions
Copy link

Also available in: Atom PDF