Bug 1221442

Summary: [Build 64.2] openQA test fails in zypper_migration - Valid metadata not found at specified URL
Product: [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 Reporter: Lemon Li <leli>
Component: Media ContentAssignee: Radoslav Tzvetkov <rtsvetkov>
Status: RESOLVED INVALID QA Contact: Radoslav Tzvetkov <rtsvetkov>
Severity: Normal    
Priority: P5 - None CC: chcao
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: SLES 15   
URL: https://openqa.suse.de/tests/13784938/modules/zypper_migration/steps/5
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper log
zypper migration journal log
autoinst log

Description Lemon Li 2024-03-15 01:22:54 UTC
Created attachment 873526 [details]
zypper log

## Observation
This is online migration test, after run zypper migration, it failed for 'Valid metadata not found at specified URL'.

It seems failed for 'Signature verification':
###
[SUSE_Linux_Enterprise_High_Performance_Computing_15_SP6_x86_64:SLE-Product-HPC-15-SP6-Pool|http://openqa.suse.de/assets/repo/SLE-15-SP6-Product-HPC-POOL-x86_64-Build64.2-Media1/] Valid metadata not found at specified URL
  History:
   - Signature verification failed for repomd.xml
   - Can&apos;t provide /repodata/repomd.xml
###

openQA test in scenario sle-15-SP6-Migration-from-SLE15-SPx-x86_64-migr_slehpc15sp3@64bit fails in
[zypper_migration](https://openqa.suse.de/tests/13784938/modules/zypper_migration/steps/5)

## Test suite description
Online migration from slehpc15 sp3 with addons of base,desktop,dev,hpcm,serverapp,python2,wsm,ltss. Migration via zypper. Origin system has system role textmode and default patterns.


## Reproducible

Fails since (at least) Build [64.2](https://openqa.suse.de/tests/13784938) (current job)


## Expected result

Last good: (unknown) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Migration-from-SLE15-SPx&machine=64bit&test=migr_slehpc15sp3&version=15-SP6)
Comment 1 Lemon Li 2024-03-15 01:23:44 UTC
Created attachment 873527 [details]
zypper migration journal log
Comment 2 Lemon Li 2024-03-15 01:24:16 UTC
Created attachment 873528 [details]
autoinst log
Comment 3 Lemon Li 2024-03-15 01:33:19 UTC
The same issue on SLES repo:
https://openqa.suse.de/tests/13784986#step/zypper_migration/8
https://openqa.suse.de/tests/13784815#step/zypper_migration/7
####
2024-03-14 16:01:43 <5> susetest(13752) [zypp-core] Exception.cc(log):186 repos.cc(build_cache):458 CAUGHT:   [SUSE_Linux_Enterprise_Server_15_SP6_x86_64:SLE-Product-SLES15-SP6-Updates|http://openqa.suse.de/assets/repo/SLE-15-SP6-Product-SLES-POOL-x86_64-Build64.2-Media1/] Valid metadata not found at specified URL
2024-03-14 16:01:43 <5> susetest(13752) [zypp-core] Exception.cc(log):186 History:
2024-03-14 16:01:43 <5> susetest(13752) [zypp-core] Exception.cc(log):186  - Signature verification failed for repomd.xml
2024-03-14 16:01:43 <5> susetest(13752) [zypp-core] Exception.cc(log):186  - Can't provide /repodata/repomd.xml
###
Comment 4 Lemon Li 2024-03-15 02:05:24 UTC
Please help confirm whether the issue of Import untrusted gpg key during yast migration is the same bug or not, https://openqa.suse.de/tests/13784829#step/yast2_migration/6
Comment 5 Chenzi Cao 2024-03-15 02:28:48 UTC
(In reply to Ming Li from comment #0)
> Created attachment 873526 [details]
> zypper log
> 
> ## Observation
> This is online migration test, after run zypper migration, it failed for
> 'Valid metadata not found at specified URL'.
> 
> It seems failed for 'Signature verification':
> ###
> [SUSE_Linux_Enterprise_High_Performance_Computing_15_SP6_x86_64:SLE-Product-
> HPC-15-SP6-Pool|http://openqa.suse.de/assets/repo/SLE-15-SP6-Product-HPC-
> POOL-x86_64-Build64.2-Media1/] Valid metadata not found at specified URL
>   History:
>    - Signature verification failed for repomd.xml
>    - Can&apos;t provide /repodata/repomd.xml
> ###

The system migrates to HPC-15-SP6, while it is supposed to migrate to SLES-15-SP6. The failure is caused by choosing the 1st product when doing migration, in this case, it should choose the 2nd product. I already file a ticket for this: https://progress.opensuse.org/issues/156409
Comment 6 Lemon Li 2024-03-15 02:33:07 UTC
To avoid the confusing for the bug and the ticket, we'd better choose a failure on SLES for a new bug.