On Tue, Jul 10, 2012 at 9:44 AM, Jean-Baptiste Denis <jbdenis(a)pasteur.fr> wrote:
Hello everybody,
I'm using 2.2.3-2.el6 from the EPEL repository.
Until today, I was using the cobbler import --available-as option to use
a remote NFS. And now, when using this command :
cobbler import --name=centos --path=/var/ftp/pub/centos/
--available-as=nfs://mynfsserver:/vol/web/ftp/pub/computing/linux/centos
everything is saved in /var/www/cobbler/ks_mirror.
The documentation
(
https://github.com/cobbler/cobbler/wiki/Using%20Cobbler%20Import) is
quite clear on the subject,
see "Alternative set-up from existing filesystem" :
"The above command will set up cobbler automatically using all of the
above distros (stored on the remote filer) -- but will keep the trees on
NFS. This saves disk space on the Cobbler server."
This seems like a (important) bug to me. Do you confirm or did I miss
something ?
This is a known issue, and has been broken since we moved to import
modules (2.2.0). The fix will be in 2.4.0, which will be the next
release.
The issue is that in order for the auto-detection to work, cobbler has
to have something to scan. The easiest fix for that was to have it
download everything temporarily (with obvious downsides...). The fix
is that we implement a white-list of files to grab when using
--available-as, so it only grabs the files it really needs in order to
scan the files correctly.
In the meantime, you can just delete the tree in ks_mirror after doing
an import with --available-as (except for the kernel/initrd files).