Bug 687951

Summary: PATCH: cobblerd restart fails when managing DHCP
Product: Red Hat Satellite 5 Reporter: Aron Parsons <aparsons>
Component: OtherAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 540CC: amoralej, clasohm, cperry, ddevaraj, nobody, pep
Target Milestone: ---Keywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-18 12:38:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 818987    
Attachments:
Description Flags
cobbler-close-file-descriptors.patch none

Description Aron Parsons 2011-03-15 19:48:03 UTC
Description of problem:
Yes, I am aware that Cobbler is not supported in this fashion.  However, many people do use the Cobbler instance provided by Satellite beyond the supported purpose.

When Cobbler has "manage_dhcp" enabled and it is managing ISC DHCP, it fails to restart because there are still open file descriptors.  This was addressed in upstream Cobbler, but the version within Satellite seems to be at an odd patch level and this fix was not included.  The upstream commit that fixed it was 1a7c17cdd5325008b2f5337f0066a242a406bfa3.

Since that patch doesn't apply to Satellite's version of Cobbler, the attached patch resolves Cobbler not being able to restart when it is managing DHCP.


Version-Release number of selected component (if applicable):
cobbler-2.0.7-5.el5sat

How reproducible:
always

Steps to Reproduce:
1. enable 'manage_dhcp' in /etc/cobbler/settings
2. service cobblerd start
3. service dhcpd start
4. cobbler sync
5. service cobblerd restart
  
Actual results:
[root@satellite cobbler]# service cobblerd restart
Stopping cobbler daemon:                                   [  OK  ]
Starting cobbler daemon:                                   [  OK  ]
[root@satellite cobbler]# Traceback (most recent call last):
  File "/usr/bin/cobblerd", line 91, in main
    app.core(api)
  File "/usr/lib/python2.4/site-packages/cobbler/cobblerd.py", line 50, in core
    do_xmlrpc_tasks(bootapi, settings, xmlrpc_port)
  File "/usr/lib/python2.4/site-packages/cobbler/cobblerd.py", line 68, in do_xmlrpc_tasks
    do_xmlrpc_rw(bootapi, settings, xmlrpc_port)
  File "/usr/lib/python2.4/site-packages/cobbler/cobblerd.py", line 107, in do_xmlrpc_rw
    server = remote.CobblerXMLRPCServer(('127.0.0.1', port))
  File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1738, in __init__
    SimpleXMLRPCServer.SimpleXMLRPCServer.__init__(self,args)
  File "/usr/lib64/python2.4/SimpleXMLRPCServer.py", line 473, in __init__
    SocketServer.TCPServer.__init__(self, addr, requestHandler)
  File "/usr/lib64/python2.4/SocketServer.py", line 330, in __init__
    self.server_bind()
  File "/usr/lib64/python2.4/SocketServer.py", line 341, in server_bind
    self.socket.bind(self.server_address)
  File "<string>", line 1, in bind
error: (98, 'Address already in use')

[root@satellite cobbler]# service cobblerd status
cobblerd dead but subsys locked
[root@satellite cobbler]# 


Expected results:
[root@satellite cobbler]# service cobblerd restart
Stopping cobbler daemon:                                   [  OK  ]
Starting cobbler daemon:                                   [  OK  ]
[root@satellite cobbler]# SERVING!


Additional info:
http://git.fedorahosted.org/git/?p=cobbler;a=commit;h=1a7c17cdd5325008b2f5337f0066a242a406bfa3

Comment 1 Aron Parsons 2011-03-15 19:48:40 UTC
Created attachment 485593 [details]
cobbler-close-file-descriptors.patch

Comment 2 Alfredo Moralejo 2011-11-15 12:26:16 UTC
Any plan to submit the patch?, I'm finding the same issue. Is there any workaround?

Comment 3 Clifford Perry 2011-11-15 16:03:36 UTC
"The upstream commit that fixed it was 1a7c17cdd5325008b2f5337f0066a242a406bfa3."

The patch is already fixed within upstream cobbler. 

If you are wanting to track and resolve this within cobbler we ship in Satellite, please note customer impacting cases. Today there is no customer association to this bug report and it is off low priority for the team.

The work-around is manually applying the proposed patch on system being impacted. 

Cliff