Attempting to register or run a zypper ref returns Valid metadata not found at specified URL(s)
This document (7013434) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 11 Service Pack 2
SUSE Linux Enterprise Server 11 Service Pack 3
SUSE Linux Enterprise Desktop 11 Service Pack 2
SUSE Linux Enterprise Desktop 11 Service Pack 3
Situation
While attempting to register a SLE 11 SP2 or SP3 system errors about Valid metadata not found at specified URL(s) are returned for one or more of the repositories that look something like the following:
Repository 'SLES11-SP3-Pool' is invalid.
Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'SLED11-SP3-Pool' because of the above error.
Repository 'SLES11-SP3-Pool' is invalid.
Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'SLED11-SP3-Pool' because of the above error.
Resolution
Check the versions of the libgpg-error0 files (there is only 1 file in i586 systems)
rpm -qa | grep libgpg-error0
libgpg-error0-1.6-8.6
libgpg-error0-32bit-1.6-8.6
If those are the versions that show on the system do the following:
1. Get the following files from the SLE 11 SP2 or SP3 Media (the iso or DVD that matches the version of your system):
The versions shown are for SLE 11 SP2 but the SP3 files are in the same location.
/suse/x86_64/libgpg-error0-1.10-0.7.29.x86_64.rpm
/suse/x86_64/libgpg-error0-32bit-1.10-0.7.29.x86_64.rpm
/suse/noarch/suse-build-key-1.0-907.37.10.noarch.rpm
2. Copy them to the server and do the following:
rpm -Uvh libgpg-error0*
rpm -e --nodeps suse-build-key
rpm -Uvh suse-build-key-1.0-907.37.10.noarch.rpm (replacing the SP3 version if necessary)
3. run zypper ref
The zypper ref should refresh all applicable repositories without the "Valid metadata" errors.
rpm -qa | grep libgpg-error0
libgpg-error0-1.6-8.6
libgpg-error0-32bit-1.6-8.6
If those are the versions that show on the system do the following:
1. Get the following files from the SLE 11 SP2 or SP3 Media (the iso or DVD that matches the version of your system):
The versions shown are for SLE 11 SP2 but the SP3 files are in the same location.
/suse/x86_64/libgpg-error0-1.10-0.7.29.x86_64.rpm
/suse/x86_64/libgpg-error0-32bit-1.10-0.7.29.x86_64.rpm
/suse/noarch/suse-build-key-1.0-907.37.10.noarch.rpm
2. Copy them to the server and do the following:
rpm -Uvh libgpg-error0*
rpm -e --nodeps suse-build-key
rpm -Uvh suse-build-key-1.0-907.37.10.noarch.rpm (replacing the SP3 version if necessary)
3. run zypper ref
The zypper ref should refresh all applicable repositories without the "Valid metadata" errors.
Cause
The libgpg-error0 rpms are the SLE 11 SP1 versions (ie 1.6-8.6) which in turn puts the gpg keyring at SLE 11 SP1 values make the gpg key checks fail and invalidating the repository.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7013434
- Creation Date: 09-Oct-2013
- Modified Date:04-Oct-2022
-
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
