Re: question on RHEL6 yum updates

Progress.....

Going to the RHN page for the system on rhn.redhat.com and removing the checkmark for the "location aware updates", I am now able to use yum to get updates as long as the serverURL is NOT using SSL. (maintaining http as the protocol instead of https).

If I edit the serverURL back to https, I receive the same error "Cannot retrieve repository metadata (repomd.xml)"


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of inode0
Sent: Tuesday, November 16, 2010 11:34 PM
To: Discussions about Red Hat Network (rhn.redhat.com)
Subject: Re: [rhn-users] question on RHEL6 yum updates

On Tue, Nov 16, 2010 at 10:53 PM, Caetano, Greg <[email protected]> wrote:
> I am working with a custom distribution and see the following behavior when doing a "yum update" to
> rhn.redhat.com
>
> [root@dl360g306]# rpm -qa yum
> yum-3.2.27-14.el6_0.1.noarch
> [root@dl360g306]# rpm -q --whatprovides /etc/sysconfig/rhn/up2date
> rhn-client-tools-1.0.0-38.el6.noarch
> [root@dl360g306]# rhn_check
>
> [root@dl360g306]# yum update
> Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security
> Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-i386-server-6. Please verify its path
> and try again
>
>
> If I edit /etc/sysconfig/rhn/up2date and change the protocol from https to https by modifying the serverURL
> serverURL=http://xmlrpc.rhn.redhat.com/XMLRPC
>
>
> [root@dl360g306]# yum update
> Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security
> rhel-i386-server-6                                                                                           | 1.8 kB     00:00
> Error: failed to retrieve
> repodata/216454a6b5f351413c3656390b31f2c2cf4a1496b333d7ecb950c258a001ca99-primary.xml.gz from
> rhel-i386-server-6
> error was [Errno 14] Peer cert cannot be verified or peer cert invalid
>
> Suggestions?

While I haven't seen this yet with RHEL6 it is getting to be a fairly
common sight with RHEL5. Usual causes I think are being unlucky enough
to try to update while the metadata is still rebuilding after new
updates have been pushed or the CDN node you happen to be connecting
to just has broken metadata.

In the first case it clears up usually in an hour or two. In the
second case it can last longer. You can disable using CDN on that
machine's RHN system page preferences and see if that helps.

John

_______________________________________________
rhn-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhn-users