SUSE Support

Here When You Need Us

"RepoMDError: Cannot access repository" when syncing Red Hat (native) channels through CDN in SUSE Manager

This document (000020574) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 4.2
SUSE Manager 4.1

Situation

Following the documentation to set up Red Hat channels, populating them with packages coming from their CDN (Content Delivery Network), the sync process will fail. Logs in /var/log/rhn/reposync will show the following relevant lines:

File 'repomd.xml' from repository 'rhel-x86_64-server-7-os' is unsigned, continue? [yes/no] (no): no error]
10:38:23 RepoMDError: Cannot access repository. Repository 'rhel-x86_64-server-7-os' is invalid. ...
Valid metadata not found at specified URL

Resolution

The usual problem here is that when setting up the repository (needed in order to feed the custom channel created afterwards), there is an option called "Has signed metadata?" which is checked by default. Even if this is stated in the documentation, as it is a long procedure, sometimes it can be accidentally overlooked. Most of the time, simply unchecking this option in the web-UI ("Software - Manage - Repositories - Click on affected Repositories - Uncheck 'has signed metadata?' - Update repository") will solve the issue. After changing the option, the sync can be tested again in the web-UI: "Software - Manage - Channels - Click on affected channel associated to the repository - Repositories tab - Sync subtab - Click on 'Sync now' ", and the error should be gone.

Other conflicts could be regarding networking: connections to the CDN URL (usually cdn.redhat.com) should be bypassed in any proxy or firewall on the network, and obviously the proxy (in case one needs to be used) should be properly set up in the SUSE Manager, in both Yast configuration ("yast proxy") and the SUSE Manager web-UI (admin menu, setup wizard, http proxy). Both configurations have an option to be tested.

Cause

The access to the repository is already set up through the certificates, so enabling the option "Has signed metadata" when setting up the repository will not work.
As for the other possible problems, a network connection is always needed. If there's a firewall blocking connections, or a proxy that has not been properly set up, it will not be possible to download anything from the CDN.

Additional Information

See related documentation:
https://documentation.suse.com/suma/4.2/en/suse-manager/client-configuration/clients-rh-cdn.html
https://documentation.suse.com/external-tree/en-us/suma/4.1/suse-manager/client-configuration/clients-rh-cdn.html

Please notice that this article is not relevant for customers using SUSE Linux Enterprise Server with Expanded Support.

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:000020574
  • Creation Date: 01-Feb-2022
  • Modified Date:04-Feb-2022
    • SUSE Manager

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

tick icon

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

tick icon

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

tick icon

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.