> > Am trying to configure my repos in Cobbler so that it > automagically downloads and manages the updates, etc. Did > these steps... > > > > Hmmm. This generally works. > > You might have just had a connectivity problem with mirrorservice?
I did wonder that (proxy maybe), but as mentioned I can wget, yum and reposync as normal. More telling (I'd guess) is that reposync works by itself. IIRC cobbler reposync just uses reposync. Correct??? Was wondering if it is a proxy issue however. However the fact that reposync works, kind of kills that idea (unless I am mistaken about how reposync is utilised/called). For example... [EMAIL PROTECTED] ~]# cat /etc/yum.repos.d/CentOS-Base.repo #released updates [updates] name=CentOS-$releasever - Updates baseurl=http://www.mirrorservice.org/sites/mirror.centos.org/5/updates/i386/ #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 [EMAIL PROTECTED] ~]# cat /etc/yum.conf [main] cachedir=/var/cache/yum keepcache=1 debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest distroverpkg=redhat-release tolerant=1 exactarch=1 obsoletes=1 gpgcheck=1 plugins=1 metadata_expire=1800 # PUT YOUR REPOS HERE OR IN separate files named file.repo # in /etc/yum.repos.d proxy=http://proxy.ad.kew.org:8080 [EMAIL PROTECTED] ~]# mkdir test [EMAIL PROTECTED] ~]# reposync -a i386 -r updates -p test/ Loading "installonlyn" plugin Downloading Cluster_Administration-as-IN-5.2-1.el5.centos.noarch.rpm Downloading Cluster_Administration-bn-IN-5.2-1.el5.centos.noarch.rpm Downloading Cluster_Administration-de-DE-5.2-1.el5.centos.noarch.rpm <snipped> So it seems reposync works as expected. However using cobbler reposync it still fails. > > Where the exact same options used? > > If you rm -rf > /var/www/cobbler/repo_mirror/CentOS5-i386updates and retry > the command, what happens? I get the same error as last time :( [EMAIL PROTECTED] ~]# rm -rf /var/www/cobbler/repo_mirror/CentOS5* (also deleted the .origin dir) [EMAIL PROTECTED] ~]# ls /var/www/cobbler/repo_mirror/ [EMAIL PROTECTED] ~]# cobbler reposync - creating: /var/www/cobbler/repo_mirror/.origin/CentOS5-i386updates.repo - /usr/bin/reposync --config=/var/www/cobbler/repo_mirror/.origin/CentOS5-i386updates.repo --repoid=CentOS5-i386updates --download_path=/var/www/cobbler/repo_mirror -a i386 Traceback (most recent call last): File "/usr/bin/reposync", line 196, in ? main() File "/usr/bin/reposync", line 140, in main my.doRepoSetup() File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 306, in doRepoSetup repo.setup(self.conf.cache) File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 498, in setup raise Errors.RepoError, ('Cannot open/read repomd.xml file for repository: %s' % self) yum.Errors.RepoError: Cannot open/read repomd.xml file for repository: CentOS5-i386updates cobbler reposync failed > FYI -- You can get the RPMs from EPEL testing as per the download > instructions page to save yourself some work. EPEL rolls monthly, > testing rolls much more frequently. There is no "testing" policy so > there is no reason to think normal EPEL is more/less stable, > basically... as weird as that sounds. Oh, OK, either way :) Thanks Dan -- Dan Hawker [EMAIL PROTECTED] UNIX & Comms Royal Botanic Gardens - Kew -- "I love deadlines. I like the whooshing sound they make as they fly by" - Douglas Adams -- _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
