Perry Myers
2008-Dec-28 05:02 UTC
[Ovirt-devel] cobbler import of a repo with only noarch packages in it
I'm trying to do a cobbler import of a directory structure that only has noarch packages in it. I'm using the import to create a minimal pxe boot environment without needing to mirror all of the packages (we just use external repos for the packages) However, when I try to do a cobbler import of a directory structure that only contains noarch packages I get the following error:> + cobbler import --name=Fedora-10 --arch=x86_64 --path=/var/www/cobbler/ks_mirror/Fedora-10-x86_64 > sending incremental file list > > sent 392 bytes received 16 bytes 816.00 bytes/sec > total size is 134808812 speedup is 330413.75 > Given arch (x86_64) not found on imported tree /var/www/cobbler/ks_mirror/Fedora-10-x86_64/Packages > > - rsync -a '/var/www/cobbler/ks_mirror/Fedora-10-x86_64/' /var/www/cobbler/ks_mirror/Fedora-10-x86_64 --exclude-from=/etc/cobbler/rsync.exclude --progress > ---------------- (adding distros) > - found content (breed=redhat) at /var/www/cobbler/ks_mirror/Fedora-10-x86_64/images/pxebootI know in the past we were able to import a directory structure with only noarch packages and still specify an arch (x86_64 or i386) and it didn't fail like above. Is this a recent change or restriction? Should we just add a single arch specific package to the directory structure to get around this? Thanks, Perry -- |=- Red Hat, Engineering, Emerging Technologies, Boston -=| |=- Email: pmyers at redhat.com -=| |=- Office: +1 412 474 3552 Mobile: +1 703 362 9622 -=| |=- GnuPG: E65E4F3D 88F9 F1C9 C2F3 1303 01FE 817C C5D2 8B91 E65E 4F3D -=|
Perry Myers
2008-Dec-28 05:05 UTC
[Ovirt-devel] cobbler import of a repo with only noarch packages in it
Perry Myers wrote:> I'm trying to do a cobbler import of a directory structure that only has > noarch packages in it. I'm using the import to create a minimal pxe > boot environment without needing to mirror all of the packages (we just > use external repos for the packages) > > However, when I try to do a cobbler import of a directory structure that > only contains noarch packages I get the following error: >> + cobbler import --name=Fedora-10 --arch=x86_64 >> --path=/var/www/cobbler/ks_mirror/Fedora-10-x86_64 >> sending incremental file list >> >> sent 392 bytes received 16 bytes 816.00 bytes/sec >> total size is 134808812 speedup is 330413.75 >> Given arch (x86_64) not found on imported tree >> /var/www/cobbler/ks_mirror/Fedora-10-x86_64/Packages >> >> - rsync -a '/var/www/cobbler/ks_mirror/Fedora-10-x86_64/' >> /var/www/cobbler/ks_mirror/Fedora-10-x86_64 >> --exclude-from=/etc/cobbler/rsync.exclude --progress >> ---------------- (adding distros) >> - found content (breed=redhat) at >> /var/www/cobbler/ks_mirror/Fedora-10-x86_64/images/pxeboot > > I know in the past we were able to import a directory structure with > only noarch packages and still specify an arch (x86_64 or i386) and it > didn't fail like above. Is this a recent change or restriction? Should > we just add a single arch specific package to the directory structure to > get around this?So, for those of you using the 0.96 release or building new appliances from the development repositories it appears that a new version of cobbler in Fedora has broken the ovirt-appliance. I've posted the above question to the cobbler mailing list to find out if this was an intended change or something that recently broke in cobbler. Hopefully it is the latter and an update to the cobbler package will fix this. The alternative is that we need to change the appliance build procedure to account for this change and we'll have to do a 0.96-2 release to fix this. Thanks, Perry
James Cammarata
2008-Dec-28 06:13 UTC
[Ovirt-devel] Re: cobbler import of a repo with only noarch packages in it
On Sun, 28 Dec 2008 00:02:03 -0500, Perry Myers <pmyers at redhat.com> wrote:> I'm trying to do a cobbler import of a directory structure that only has > noarch packages in it. I'm using the import to create a minimal pxe boot > environment without needing to mirror all of the packages (we just use > external repos for the packages) > > However, when I try to do a cobbler import of a directory structure that > only contains noarch packages I get the following error: >> + cobbler import --name=Fedora-10 --arch=x86_64 > --path=/var/www/cobbler/ks_mirror/Fedora-10-x86_64 >> sending incremental file list >> >> sent 392 bytes received 16 bytes 816.00 bytes/sec >> total size is 134808812 speedup is 330413.75 >> Given arch (x86_64) not found on imported tree > /var/www/cobbler/ks_mirror/Fedora-10-x86_64/Packages >> >> - rsync -a '/var/www/cobbler/ks_mirror/Fedora-10-x86_64/' > /var/www/cobbler/ks_mirror/Fedora-10-x86_64 > --exclude-from=/etc/cobbler/rsync.exclude --progress >> ---------------- (adding distros) >> - found content (breed=redhat) at > /var/www/cobbler/ks_mirror/Fedora-10-x86_64/images/pxeboot > > I know in the past we were able to import a directory structure with only > noarch packages and still specify an arch (x86_64 or i386) and it didn't > fail like above. Is this a recent change or restriction? Should we just > add a single arch specific package to the directory structure to get > around this? > > Thanks, > > PerryWhat version of cobbler are you running? I know there were a lot of changes to the import stuff for debian recently, including how it detected the arch from the tree automatically, it's possible if you're running a newer version that functionality may have been broken inadvertently. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Perry Myers
2008-Dec-28 06:20 UTC
[Ovirt-devel] Re: cobbler import of a repo with only noarch packages in it
James Cammarata wrote:> On Sun, 28 Dec 2008 00:02:03 -0500, Perry Myers <pmyers at redhat.com> wrote: >> I'm trying to do a cobbler import of a directory structure that only has >> noarch packages in it. I'm using the import to create a minimal pxe boot >> environment without needing to mirror all of the packages (we just use >> external repos for the packages) >> >> However, when I try to do a cobbler import of a directory structure that >> only contains noarch packages I get the following error: >>> + cobbler import --name=Fedora-10 --arch=x86_64 >> --path=/var/www/cobbler/ks_mirror/Fedora-10-x86_64 >>> sending incremental file list >>> >>> sent 392 bytes received 16 bytes 816.00 bytes/sec >>> total size is 134808812 speedup is 330413.75 >>> Given arch (x86_64) not found on imported tree >> /var/www/cobbler/ks_mirror/Fedora-10-x86_64/Packages >>> - rsync -a '/var/www/cobbler/ks_mirror/Fedora-10-x86_64/' >> /var/www/cobbler/ks_mirror/Fedora-10-x86_64 >> --exclude-from=/etc/cobbler/rsync.exclude --progress >>> ---------------- (adding distros) >>> - found content (breed=redhat) at >> /var/www/cobbler/ks_mirror/Fedora-10-x86_64/images/pxeboot >> >> I know in the past we were able to import a directory structure with only >> noarch packages and still specify an arch (x86_64 or i386) and it didn't >> fail like above. Is this a recent change or restriction? Should we just >> add a single arch specific package to the directory structure to get >> around this? >> >> Thanks, >> >> Perry > > > What version of cobbler are you running? I know there were a lot of > changes to the import stuff for debian recently, including how it detected > the arch from the tree automatically, it's possible if you're running a > newer version that functionality may have been broken inadvertently. >I'm running 1.4.0-2 and I think I found the problem... You're right it is with the arch detection. Even though I pass --arch to the cobbler import manually, it still tries to verify the arch by looking specifically at the kernel-headers package located in the path that you are importing from. Problem is, our minimal tree didn't even have kernel-headers in it. To fix the problem I'm just going to add kernel-headers package into our tree. That seems to work. Thanks, Perry -- |=- Red Hat, Engineering, Emerging Technologies, Boston -=| |=- Email: pmyers at redhat.com -=| |=- Office: +1 412 474 3552 Mobile: +1 703 362 9622 -=| |=- GnuPG: E65E4F3D 88F9 F1C9 C2F3 1303 01FE 817C C5D2 8B91 E65E 4F3D -=|
Michael DeHaan
2008-Dec-30 23:37 UTC
[Ovirt-devel] Re: cobbler import of a repo with only noarch packages in it
Perry Myers wrote:> I'm trying to do a cobbler import of a directory structure that only has > noarch packages in it. I'm using the import to create a minimal pxe boot > environment without needing to mirror all of the packages (we just use > external repos for the packages) > > However, when I try to do a cobbler import of a directory structure that > only contains noarch packages I get the following error: > >> + cobbler import --name=Fedora-10 --arch=x86_64 --path=/var/www/cobbler/ks_mirror/Fedora-10-x86_64 >> sending incremental file list >> >> sent 392 bytes received 16 bytes 816.00 bytes/sec >> total size is 134808812 speedup is 330413.75 >> Given arch (x86_64) not found on imported tree /var/www/cobbler/ks_mirror/Fedora-10-x86_64/Packages >> >> - rsync -a '/var/www/cobbler/ks_mirror/Fedora-10-x86_64/' /var/www/cobbler/ks_mirror/Fedora-10-x86_64 --exclude-from=/etc/cobbler/rsync.exclude --progress >> ---------------- (adding distros) >> - found content (breed=redhat) at /var/www/cobbler/ks_mirror/Fedora-10-x86_64/images/pxeboot >> > > I know in the past we were able to import a directory structure with only > noarch packages and still specify an arch (x86_64 or i386) and it didn't > fail like above. Is this a recent change or restriction? Should we just > add a single arch specific package to the directory structure to get > around this? > > Thanks, > > Perry > >It seems you want "cobbler repo add" and not "import", as you're talking more about a noarch repo than an install tree. I don't see how you could get an installable distribution with just noarch packages :) Import is for install trees, which can also be used as repos, yes. But repos are not == install trees. Does that make sense or did I miss something? If you're doing something really simple "cobbler distro add" alone might suffice, though I'd like to understand a little more about the use case to say for sure. --Michael