On Fri, Jun 8, 2012 at 5:09 PM, Greg Swift
<gregswift(a)gmail.com> wrote:
> On Fri, Jun 8, 2012 at 4:40 PM, Nishanth Aravamudan
> <nacc(a)linux.vnet.ibm.com> wrote:
>> On 08.06.2012 [14:35:16 -0700], Nishanth Aravamudan wrote:
>>> On 08.06.2012 [15:18:32 -0500], Greg Swift wrote:
>>> > On Fri, Jun 8, 2012 at 1:42 PM, Dan Rao <dhananja(a)cs.wisc.edu>
wrote:
>>> > > Hi all,
>>> > >
>>> > > I upgraded my Cobbler install to 2.2.3-1.el6 (from epel-testing)
last
>>> > > night.
>>> > >
>>> > > Interestingly, when I run cobbler sync, only machines that have
netboot
>>> > > enabled get entries in my dhcpd.conf.
>>> > >
>>> > > The offending line(s) appear to be in
>>> > > /usr/lib/python2.6/site-packages/cobbler/modules/manage_isc.py -
lines
>>> > > 164-165
>>> > >
>>> > > ----
>>> > > if not interface["netboot_enabled"]:
>>> > > continue
>>> > > ----
>>> > >
>>> > > (This is in the section that generates the ISC dhcpd config
file).
>>> > >
>>> > >
>>> > > I commented those lines out to get my server back, but I was
curious as
>>> > > to why that was there in the first place.
>>> > >
>>> > > Any insight would be appreciated!
>>> >
>>> > It appears that this was added to prevent ppc64 reboot loops.
>>> >
https://github.com/cobbler/cobbler/commit/bc76631ea158c76b1cdc8d3af28c9dc...
>>> >
>>> > I know that we had the potential for reboot loops even on regular x86
>>> > hardware, but we dealt with it without code change. Our systems boot
>>> > harddrive then netboot. So on initial install they netboot, once
>>> > there is an OS they regular boot. If you need to re-install you
>>> > either use koan or function key to select network boot at boot time.
>>>
>>> That sounds ... not stand-alone :)
>>>
>>> > That being said, our systems also turn static post-install, so this
>>> > change would not affect us. However, if we ran off DHCP period we
>>> > would have the same issue you are experiencing with this.
>>> >
>>> > Maybe the better check would be:
>>> >
>>> > if not interface["netboot_enabled"] and
interface['static']:
>>> > continue
>>> >
>>> > ?
>>>
>>> Well, this actually perhaps points at my ignorance -- I think that if
>>> you want Cobbler to manage DHCP, you mean to allow it to manage DHCP for
>>> its purposes (which are transparent to yours). But if you want to have
>>> DHCP be a persistent thing (unrelated to Cobbler's interactions), then
>>> you probably should be managing it outside of Cobbler (at least, IMHO).
>>> Or that's how I thought it was being used ... I hadn't considered
the
>>> case of using DHCP outside the netbooting case.
>>
>> And I will now affirm my own ignorance, after re-reading the main
>> Cobbler page:
>>
>> "Cobbler can also optionally help with managing DHCP, DNS, and yum
>> package mirroring infrastructure -- in this regard, it is a more
>> generalized automation app, rather than just dealing specifically with
>> installations."
>>
>> So, to that end, the above change is needed and I apologize for the
>> disruption.
>
> it happens :) you meant well, and it is a nice change overall, as my
> environment benefits from the concept, because now i don't care about
> my boot order as much :)
>
> -greg
Dan and Nishanth,
Did you try out the different conditional logic to see if it meets you
needs?
I'm testing it now in my environment, need to run a few more jobs, but
it seems fine here.
Thanks,
Nish
--
Nishanth Aravamudan <nacc(a)us.ibm.com>
IBM Linux Technology Center