Re: question on RHEL6 yum updates

inode0 <[email protected]> Tue, 16 Nov 2010 23:33:55 -0600
Newsgroups gmane.linux.redhat.rhn.user
Message-ID <[email protected]>
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 wh=
en 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: r=
hel-i386-server-6. Please verify its path
> and try again
>
>
> If I edit /etc/sysconfig/rhn/up2date and change the protocol from https t=
o https by modifying the serverURL
> serverURL=3Dhttp://xmlrpc.rhn.redhat.com/XMLRPC
>
>
> [root@dl360g306]# yum update
> Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security
> rhel-i386-server-6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 1.8 kB =A0 =A0 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