[tools] mrepo not creating metadata for old yum

[David Gillies]

On Wed, 2008-08-20 at 11:37 +0300, urgrue wrote:
> David Gillies wrote:
> > On Wed, 2008-08-20 at 10:06 +0300, urgrue wrote:
> >> I've got mrepo set up and serving rhel as5 (this works). Im trying
> to
> >> add 4WS and 4AS. These don't. I think the reason is because mrepo
> is not
> >> creating the headers file/dir that yum wants.
> >> My 4AS and 4WS clients use yum 2.0.7, and the 4AS section in my
> >> mrepo.conf contains metadata = yum repomd repoview
> >>
> >> Running mrepo -ugvv it doesn't complain about anything, and
> successfully
> >> downloads updates and also creates the repodata directory for newer
> yum.
> >> But I don't see the headers dir for older yum.
> >>
> >> Client-side it looks like this:
> >> retrygrab() failed for:
> >> http://mrepo.server.com/mrepo/4WS-i386/RPMS.all/headers/header.info
> >> Executing failover method
> >> failover: out of servers to try
> >> Error getting file
> >> http://install.elma.fi/mrepo/4WS-i386/RPMS.all/headers/header.info
> >> [Errno 4] IOError: HTTP Error 404: Not Found
> >>
> >> Any ideas?
> > 
> > If you want to run your rhel4 servers with yum 2.0.x, you'll need to
> > make sure you have yum-arch installed on your mrepo server to
> generate
> > the older style yum metadata. The yum-arch rpm is available from the
> > EPEL repository.
> > 
> >
> http://download.fedora.redhat.com/pub/epel/5/i386/repoview/yum-arch.html
> > 
> > Probably the best thing to do is just upgrade yum on your rhel4
> servers
> > to the 2.4.x versions so that they can use the repodata metadata
> instead.
> > 
> 
> Thanks for your reply.
> I'll resort to updating yum if I have to but I'd rather just fix mrepo
> if possible. Company policy doesn't really allow altering some of
> these
> old systems in any way so doing a yum update on all AS4's is a way
> bigger pain for me.
> 
> I do have yum-arch installed and I now also added yumarchcmd =
> /usr/bin/yum-arch to mrepo.conf, but it still doesnt work. Still no
> headers dir.
> mrepo -ugvvvv output contains:
> Setting option yumarchcmd in section [main] to: /usr/bin/yum-arch
> And no errors of any kind.
> 
Have you tried running yum-arch from the command line against the repos?
I had problems with yum-arch in the past and I found that none of the
errors that it was spitting out was getting passed to mrepo.

For me when yum-arch was silently failing it was because the mrepo
server didn't have any of the rpm GPG keys installed for the various
repos, and therefore it was deciding (understandably) that they were
untrusted packages.

Regards,
David Gillies
Systems Engineer
Digital Infrastructure Services
Fairfax Digital