Build server requires calling cobbler sync before deploying nodes

Bug #1173401 reported by subconscious
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cisco Openstack
Fix Committed
Critical
Unassigned

Bug Description

After multiple installs of a build server: each time an additional "cobbler sync" needs to be executed in order for dnsmasq to offer a lease.

Associated errors:

Fri Apr 26 18:18:23 2013 - INFO | Exception Info:
  File "/usr/lib/python2.7/dist-packages/cobbler/remote.py", line 1944, in _dispatch
    return method_handle(*params)
   File "/usr/lib/python2.7/dist-packages/cobbler/remote.py", line 873, in xapi_object_edit
    handle = self.get_item_handle(object_type, object_name)
   File "/usr/lib/python2.7/dist-packages/cobbler/remote.py", line 655, in get_item_handle
    raise CX("internal error, unknown %s name %s" % (what,name))

Changed in openstack-cisco:
milestone: none → 2012.2.4
Revision history for this message
Chris Ricker (chris-ricker) wrote :

We'll probably need more steps to reproduce

In various light testing (start from bare, add more nodes, remove nodes, add nodes back) I can't get to the state of node existing cobbler but dnsmasq not aware of it / offering lease, or produce the above exception

Changed in openstack-cisco:
status: New → Incomplete
Changed in openstack-cisco:
milestone: 2012.2.4 → none
Revision history for this message
subconscious (subconscious) wrote :

I confirmed this again this morning on a virgin install. The only step I needed to correct it was to run cobbler sync on the build server then rerun ./clean-server control-server. I am thinking that instead of using

before => Service[cobbler], we use "require". I'll test this out and post results.

Changed in openstack-cisco:
milestone: none → 2012.2.4
assignee: nobody → Don Talton (dotalton)
importance: Undecided → Critical
Revision history for this message
subconscious (subconscious) wrote :

https://github.com/CiscoSystems/puppet-cobbler/pull/45

This modification appears to fix it. I tested it as working now. Basically, I dumped the package requirement and required the service instead of using before.

Changed in openstack-cisco:
status: Incomplete → Fix Committed
status: Fix Committed → In Progress
Changed in openstack-cisco:
status: In Progress → Fix Released
Changed in openstack-cisco:
status: Fix Released → Fix Committed
Revision history for this message
Abdi Ibrahim (abdi-w) wrote :

I'm running g.2 release for Grizzly and this issue still exist. After multiple install of the build-server you'll need to run 'cobbler sync' in order the PXE boot process to start and working. I'm assuming that this problem still exist.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.