Hi, I've installed a brand-new cobbler 2.4b5 server on centos6-amd64. I need to install a couple of Ubuntu12 servers with it. I've never installed Ubuntu before, much less via cobbler - so I'd be grateful for some advice. The idea is to: - install via eth1 - leave eth0 alone, or better, already give it the "final" configuration, via cobbler This works on my CentOS and RedHat installs on my "old" cobbler 2.2.3 server. Obviously, it's not so simple with Ubuntu. I've taken the sample.preseed file and adapted it minimally. One problem I have is: - if I try to enter the default gateway in the cobbler-webgui (Networking (Global)), I get problem that all leases are abandoned because somehow the interface is "up" before it gets an IP via DHCP - so, I try to set the default-gateway via a kickstart meta-parameter - the install then continues, but after the reboot, eth0 is not configured (neither is /etc/resolv.conf) - is one then supposed to run some sort of post-install script that "fixes" the network-configuration? I use $SNIPPET('network_noncore_deb') in the pressed/kickstart file, which reads: d-i netcfg/get_nameservers string $name_servers d-i netcfg/get_ipaddress string $ip_address_eth0 d-i netcfg/get_netmask string $netmask_eth0 d-i netcfg/get_gateway string $ksgateway d-i netcfg/confirm_static boolean true Another issue is that the installer tries to fetch a lot of files that just aren't in my cobbler-repo of the imported CD. How can I import the rest of the repo so that the install doesn't pause so often? A third issue is that with Ubuntu at least, if the dhcp-server does not supply a nameserver, the installation will ask for one.... So I supplied a non-existant one - but still, it bothers me a bit. Thanks in advance _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler

wrote:

wrote:

I just packaged 2.4.0 beta6 up, which includes everything I mentioned earlier. I have been testing it quite a bit and it seems pretty solid as far as Ubuntu/ESXi support goes. The above is part of the reason I keep delaying the release - I'm really trying to make this a solid release with as few new problems as possible while fixing a lot of the glaring issues that have existed for a while (sub-par ubuntu support was at the top of that list). There is one final bug that I think is a blocker for an official release ( https://github.com/cobbler/cobbler/issues/462) which is related to the new distro signatures support. Once I have that fixed, I will not do a beta 7 and will release 2.4.0 officially. So go test beta6 for now, and let me know if you find any problems - specifically with Ubuntu or ESXi 5+ builds. On Fri, May 24, 2013 at 11:02 AM, Bret Wortman <bret.wortman(a)damascusgrp.com > wrote: > Does this mean 2.4.0 is close? I've got a production shop that's waiting > with baited breath (mints close by) for the ability to use the > --available-as flag properly. I don't mean to put on pressure and am happy > to wait until it's production-ready. Just curious is all. > > > * > * > *Bret Wortman* > <http://damascusgrp.com/> > http://damascusgrp.com/ <http://bretwortman.com/> > http://about.me/wortmanbret > > > On Fri, May 24, 2013 at 11:31 AM, James Cammarata <jimi(a)sngx.net&gt; wrote: > >> I've been making a lot of improvements in this area lately, so if this is >> a brand new installation of cobbler I'd recommend you grab the master >> branch via github and use that instead. Specifically, I've been fixing: >> >> * better apt repo support, to address the issue you mention above. >> Specifically now there are not separate repos for things like -security. >> Apt repos now have two new fields (apt_dists and apt_collections) so that >> you can mirror a lot more into a single repo. There are now also snippets >> to use these new repo configurations. >> * templated late/early command scripts support >> * debian network configuration (using the above late_command script >> support) >> * per-interface network gateways (since deb/ubuntu doesn't really have a >> gateway of last resort configuration like redhat does, at least not that >> I've found). >> >> Doing network configuration during the preseed is still a bit tricky, as >> preseed has a few hoops you need to jump through and doesn't always respect >> the d-i directives you specify. You'll probably want to continue to >> manually modify the preseed to use eth1 instead if that's the way you want >> to go. >> >> If you do decide to use the master branch, be sure to back up >> /etc/cobbler, /var/lib/cobbler and /var/www/cobbler to preserve anything >> you might have done so far (make install/make webtest can/will reset some >> files to the defaults). >> >> >> >> On Fri, May 24, 2013 at 9:24 AM, Rainer Duffner <rainer(a)ultra-secure.de&gt;wrote: >> >>> Hi, >>> >>> I've installed a brand-new cobbler 2.4b5 server on centos6-amd64. >>> I need to install a couple of Ubuntu12 servers with it. >>> I've never installed Ubuntu before, much less via cobbler - so I'd be >>> grateful for some advice. >>> >>> The idea is to: >>> - install via eth1 >>> - leave eth0 alone, or better, already give it the "final" >>> configuration, via cobbler >>> >>> This works on my CentOS and RedHat installs on my "old" cobbler 2.2.3 >>> server. >>> Obviously, it's not so simple with Ubuntu. >>> >>> >>> I've taken the sample.preseed file and adapted it minimally. >>> >>> One problem I have is: >>> - if I try to enter the default gateway in the cobbler-webgui >>> (Networking (Global)), I get problem that all leases are abandoned >>> because somehow the interface is "up" before it gets an IP via DHCP >>> - so, I try to set the default-gateway via a kickstart meta-parameter >>> - the install then continues, but after the reboot, eth0 is not >>> configured (neither is /etc/resolv.conf) >>> - is one then supposed to run some sort of post-install script that >>> "fixes" the network-configuration? >>> >>> I use >>> $SNIPPET('network_noncore_deb') >>> in the pressed/kickstart file, which reads: >>> >>> d-i netcfg/get_nameservers string $name_servers >>> d-i netcfg/get_ipaddress string $ip_address_eth0 >>> d-i netcfg/get_netmask string $netmask_eth0 >>> d-i netcfg/get_gateway string $ksgateway >>> d-i netcfg/confirm_static boolean true >>> >>> >>> Another issue is that the installer tries to fetch a lot of files that >>> just aren't in my cobbler-repo of the imported CD. >>> How can I import the rest of the repo so that the install doesn't pause >>> so often? >>> >>> A third issue is that with Ubuntu at least, if the dhcp-server does not >>> supply a nameserver, the installation will ask for one.... >>> So I supplied a non-existant one - but still, it bothers me a bit. >>> >>> >>> >>> >>> >>> Thanks in advance >>> _______________________________________________ >>> cobbler mailing list >>> cobbler(a)lists.fedorahosted.org >>> https://lists.fedorahosted.org/mailman/listinfo/cobbler >>> >> >> >> _______________________________________________ >> cobbler mailing list >> cobbler(a)lists.fedorahosted.org >> https://lists.fedorahosted.org/mailman/listinfo/cobbler >> >> > > _______________________________________________ > cobbler mailing list > cobbler(a)lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/cobbler > >

Am Fri, 24 May 2013 20:15:54 -0500 schrieb James Cammarata <jimi(a)sngx.net&gt;: > I just packaged 2.4.0 beta6 up, which includes everything I mentioned > earlier. I have been testing it quite a bit and it seems pretty solid > as far as Ubuntu/ESXi support goes. Excuse me for being a bit dense - but where can I download beta6 (as an RPM)? http://dl.fedoraproject.org/pub/epel/testing/6/x86_64/ still has beta5. Or do I have to check-out via git? Best Regards, Rainer _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler

Am Mon, 27 May 2013 06:27:28 -0500 schrieb James Cammarata <jimi(a)sngx.net&gt;: > All snippets are python-cheetah templates, so what appears to be > commented-out python is actually the cheetah templating language. > > The post_install_network_config_deb script is used inside the > /var/lib/cobbler/scripts/preseed_late_default script, which is called > as the late_command in the sample.seed: > > d-i preseed/late_command string wget -O- \ > http:// $http_server/cblr/svc/op/script/$what/$name/?script=preseed_late_default > | \ > chroot /target /bin/sh -s > > Where $what is either "system" or "profile". > > To set the gateway in ubuntu, use: > > $ cobbler system edit --name=foo --interface=ethX --if-gateway=1.2.3.4 OK, so I have: [root@cobbler ~]# tail -n 5 \ /var/lib/cobbler/kickstarts/u12-noncore2.seed # packages and run commands in the target system. # d-i preseed/late_command string [command] d-i preseed/late_command string wget -O- \ http:// $http_server/cblr/svc/op/script/$what/$name/?script=preseed_late_default2 | \ chroot /target /bin/sh -s When I run that line on the shell, I get: # Start preseed_late_default # This script runs in the chroot /target by default $SNIPPET('post_install_network_config2_deb') # start late_apt_repo_config cat<<EOF>/etc/apt/sources.list deb http://cobbler-server-ip/cblr/links/Ubuntu12-x86_64 precise main EOF # end late_apt_repo_config # A general purpose snippet to add late-command actions for preseeds # Start download cobbler managed config files (if applicable) # End download cobbler managed config files (if applicable) wget "http://cobbler-server-ip/cblr/svc/op/ks/system/test-ubuntu" \ -O /var/log/cobbler.seed wget \ "http://cobbler-server-ip/cblr/svc/op/trig/mode/post/system/test-ubuntu" -O /dev/null # End preseed_late_default When I run that, I get the 4-byte file with "True" in it. No error-message in /var/log/cobbler/cobbler.log > Note from above, your variable $ksgw would not be stored in $idata > (which is the interface data for the system), rather you would put it > in --ksmeta and then get the variable with just: > > #set $ksgw = $getVar("ksgw","") Thanks, I was looking for something like this. Unfortunately, it did not help. How can I debug this? _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler

May 27 16:21:13 cobbler dhcpd: DHCPACK on 10.38.111.143 to 00:0c:29:a1:f5:b6 via eth1 May 27 16:21:13 cobbler dhcpd: Abandoning IP address 10.38.111.143: declined. May 27 16:21:13 cobbler dhcpd: DHCPDECLINE of 10.38.111.143 from 00:0c:29:a1:f5:b6 via eth1: abandoned May 27 16:21:13 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:a1:f5:b6 via eth1 May 27 16:21:14 cobbler dhcpd: DHCPOFFER on 10.38.111.144 to 00:0c:29:a1:f5:b6 via eth1 May 27 16:21:14 cobbler dhcpd: DHCPREQUEST for 10.38.111.144 (10.38.111.19) from 00:0c:29:a1:f5:b6 via eth1 May 27 16:21:14 cobbler dhcpd: DHCPACK on 10.38.111.144 to 00:0c:29:a1:f5:b6 via eth1 May 27 16:21:14 cobbler dhcpd: Abandoning IP address 10.38.111.144: declined. May 27 16:21:14 cobbler dhcpd: DHCPDECLINE of 10.38.111.144 from 00:0c:29:a1:f5:b6 via eth1: abandoned 10.38 is my pxe-network, of course and ...b6 is the MAC of the ubuntu-server to be installed. Using the shell on ALT-F2, I can see that the server has basically gobbled up all the IPs from that scope as "secondary" IPs.

Am Tue, 28 May 2013 09:04:42 -0500 schrieb James Cammarata <jimi(a)sngx.net&gt;: > Ahhh, I see, I didn't realize that you were editing the dhcp.template > earlier, sorry for the confusion. Unfortunately it doesn't look like > that information is available in the $iface structure, so you'll have > to have the correct name servers defined in the subnet area. [...] > Feel free to open an issue for this on github and I'll get it added in > permanently. Yes, it works now - thank you very, very much. Adding static routes still does not work. Is this expected, given that I don't see anything written out by the relevant section in the post_install_network_config_deb? This is really all I would need to get a system bootstrapped.... Best Regards, Rainer _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler

Actually, most of the framework was in the post snippet, this should work: