I thought I should send out an update.
I’ve been busy on other tasks & projects, & just came back to this. No updates to Spacewalk, any RPMs, no cobbler configuration changes, etc….. and now the darned thing is working. I don’t get it.
That sounds like a cobbler bug to me
Sent from my BlackBerry 10 smartphone.
Good morning, all.
I’ve apparently managed to work myself into a corner….
I’ve been running Satellite (for RHEL deployments) and Spacewalk (Oracle Linux 5, Oracle Linux 6 and CentOS6 at the moment,) for a few years. Early on in the initial Satellite deployment, I started down the road of using the underlying cobbler system for significantly more fine grained control over deployments. At this point, I’ve got a fairly well working system that will more or less figure out at runtime what needs to be installed based on physical vs virtual h/w, and cobbler fields.
Over Thanksgiving, I finally upgraded my Spacewalk server to 2.2 along with all of the underlying packages, and immediately ran into a couple of issues. One is the post-install-network-configuration snippet (fixed,) one of the Python files (also fixed,) and what I’m hoping will end up not being a major problem: using cobbler to build a bootable .iso image for a remote network no longer works.
On alt console 3, the last 4 lines displayed are (timestamps & “INFO” removed:)
only have one network device: eth0
dnsservers is x.y.z.t1,x.y.z.t2
doing kickstart… setting it up
result of pumpSetupInterface is pumpSetupInterface failed: create route – 1: Operation not permitted.
I’m reasonably sure that the cobbler system profile is proper. The profile works for a client server on the same network as the Spacewalk server when PXE booted, yet after building the .iso image, and booting from that, I get the above failure consistently. This has been an issue on every cobbler profile generated since the spacewalk upgrade. I can apparently get it to work on cobbler profiles generated prior to the upgrade and not modified since. I cannot ping the client server, even from the same subnet. It’s not getting far enough to request anything from the Spacewalk server, I’m not seeing anything in /var/log/httpd/access_log. I’ve gone so far as to build a second Spacewalk server on CentOS6 (original is running OEL5,) and am seeing the same behavior. It’s more than a little difficult to collect logs on this, as I don’t have any way to pull from the booting client server.
I don’t foresee not using this method going forward. Utilizing cobbler, koan, cheetah, etc. gives me a lot of options during the initial provisioning process. At the moment, I can survive without the .iso boot method, but down the road, I do expect some problems to crop up.
Has anyone else ran into this? I’m at a loss for where to look next.
Environment (from the test Spacewalk server:)
$ rpm -qa | egrep 'spacewalk|cobbler|syslinux' | sort
cobbler buildiso run:
task started: 2015-01-16_115932_buildiso
task started (id=Build Iso, time=Fri Jan 16 11:59:32 2015)
using/creating buildisodir: /var/cache/cobbler/buildiso
building tree for isolinux
copying miscellaneous files
copying kernels and initrds for profiles
copying kernels and initrds for systems
generating a isolinux.cfg
generating profile list
generating system list
- ksdevice bootif set for system ahdoul012
done writing config
running: mkisofs -o /home/jkalc/generated.iso -r -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -V Cobbler\ Install -R -J -T /var/cache/cobbler/buildiso
received on stdout:
received on stderr: I: -input-charset not specified, using utf-8 (detected in locale settings)
Size of boot image is 4 sectors -> No emulation
67.30% done, estimate finish Fri Jan 16 11:59:33 2015
Total translation table size: 4029
Total rockridge attributes bytes: 1320
Total directory bytes: 4700
Path table size(bytes): 40
Max brk space used 1a000
7444 extents written (14 MB)
ISO build complete
You may wish to delete: /var/cache/cobbler/buildiso
The output file is: /home/jkalc/generated.iso
*** TASK COMPLETE ***
This message may contain confidential material from Land O'Lakes, Inc. (or its subsidiary) for the sole use of the intended recipient(s) and may not be reviewed, disclosed,
copied, distributed or used by anyone other than the intended recipient(s). If you are not the intended recipient, please contact the sender by reply email and delete all copies of this message.