Kevin Collins wrote on 06/29/2007 12:00:19 PM:

> Hi,
>    I have unpacked my RHEL5 .isos onto and NFS mounted directory so
> that I can do NFS installs and NFS installs are working fine. 
> 
> I wanted to use the same install tree as a Yum repository because I
> don't want to use twice the disk space. I set up my web server, created
> a .repo file for my (as yet) non-RHN-registered RHEL5 client. I did NOT
> run createrepo on the 4 paths (Server, VT, Cluster, ClusterStorage) as
> there were already repodata directories and data there.
> 
> I confirmed that I could use yum to list to my heart's content and the
> Yum repo worked fine from that perspective. However, when I tried to
> install from one of those repos, I would get an error like the
> following:
> 
> media://1170972069.396645%233/zsh-html-4.2.6-1.i386.rpm: [Errno 4]
> IOError: <urlopen error unknown url type: media>
> 

We saw these same media:// errors until we ran the createrepo command on 
the directories. 

> So, I assumed that I needed to run the createrepo command, but also
> assumed it might break my NFS installs to do so. I backed up the
> repodata directories in my install tree and ran the createrepo. Sure
> enough, my kickstart barfs with a python stack-trace complaining about
> no available groups. 
> 
> I then put the backup repodata back into place and the kickstarts are
> working again...

We use kickstart over FTP and it works with the newly recreated .repo 
files.

> 
> So, is there any way to configure the repodata so that it will work with
> either NFS installs AND as a Yum repository? I don't want to manage 2
> copies of the same data if I can avoid it.
> 
> Thanks, 
> Kevin

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

Reply via email to