Problem logs have unexpected lines.
Typical behavior: # Start cobbler service Fri Jun 27 12:01:58 2014 - DEBUG | XMLRPC running on 25151 Fri Jun 27 12:02:15 2014 - DEBUG | XMLRPC running on 25151 # End puppet run, cobbler ready to perform job
In our logs: Tue Jun 10 12:16:09 2014 - DEBUG | API handle initialized Tue Jun 10 12:16:09 2014 - DEBUG | XMLRPC running on 25151 Tue Jun 10 12:16:09 2014 - DEBUG | API handle initialized Tue Jun 10 12:16:09 2014 - DEBUG | XMLRPC running on 25151
And after this lines we process all setup process (and most important of it: add os profiles)
To prevent situation where cobbler container can potentially report us wrong ready status i add new check https://review.openstack.org/103118
This is potentially fix, but bug is hard to reproduce and we should get new logs with this problem after merge 103118.
Problem logs have unexpected lines.
Typical behavior:
# Start cobbler service
Fri Jun 27 12:01:58 2014 - DEBUG | XMLRPC running on 25151
Fri Jun 27 12:02:15 2014 - DEBUG | XMLRPC running on 25151
# End puppet run, cobbler ready to perform job
In our logs:
Tue Jun 10 12:16:09 2014 - DEBUG | API handle initialized
Tue Jun 10 12:16:09 2014 - DEBUG | XMLRPC running on 25151
Tue Jun 10 12:16:09 2014 - DEBUG | API handle initialized
Tue Jun 10 12:16:09 2014 - DEBUG | XMLRPC running on 25151
And after this lines we process all setup process (and most important of it: add os profiles)
To prevent situation where cobbler container can potentially report us wrong ready status i add new check https:/ /review. openstack. org/103118
This is potentially fix, but bug is hard to reproduce and we should get new logs with this problem after merge 103118.