View Full Version : Error: Cannot retrieve repository metadata (repomd.xml)

21-Jul-2016, 19:45

We have a mix of redhat and suse servers in our enviornment.
We use SuSE Manager 2.1, which has all the redhat/suse channels.

Since we patch the server often, we create a clone of the updates channel every month. We subscribe the server to be patched to this cloned channel and then patch it.
This ensures that all servers of a particular project are patched to the same level.

We still have RHEL5 servers in the environment so earlier this month we created a clone of "rhel-5-x86_64-updates" channel called "rhel-5-x86_64-updates_july_2016". Today we subscribed a server to this channel and tried to run the "yum list" command, but getting "Cannot retrieve repository metadata" error. Please suggest or point me in the right direction.

[root@dmt344 ~]# more /etc/redhat-release
Red Hat Enterprise Linux Server release 5.11 (Tikanga)

[root@dmt344 ~]# yum repolist
Loaded plugins: rhnplugin, security
This system is receiving updates from RHN Classic or RHN Satellite.
repo id repo name status
rhel-5-x86_64-epel rhel 5 x86_64 epel 17,397
rhel-5-x86_64-updates_july_2016 rhel5-x86_64-updates_july_2016 0
rhel-x86_64-server-5 RHEL x86_64 Server 5 0
rhel5-x86_64-5.9-baseiso rhel5-x86_64-5.9-baseiso 0
repolist: 17,397

[root@dmt344 ~]# yum list yum
Loaded plugins: rhnplugin, security
This system is receiving updates from RHN Classic or RHN Satellite.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-5-x86_64-updates_july_2016. Please verify its path and try again


Automatic Reply
27-Jul-2016, 05:30

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- Open a service request: https://www.suse.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot..

Good luck!

Your SUSE Forums Team