Nova Conductor fails because 'service_ref' no longer global
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Running the latest nova services as of 1/21/2013 and recorded the following error from nova-conductor:
2013-01-21 17:17:36.799 CRITICAL nova [-] global name 'service_ref' is not defined
2013-01-21 17:17:36.799 TRACE nova Traceback (most recent call last):
2013-01-21 17:17:36.799 TRACE nova File "/usr/local/
2013-01-21 17:17:36.799 TRACE nova execfile(__file__)
2013-01-21 17:17:36.799 TRACE nova File "/opt/stack/
2013-01-21 17:17:36.799 TRACE nova service.wait()
2013-01-21 17:17:36.799 TRACE nova File "/opt/stack/
2013-01-21 17:17:36.799 TRACE nova _launcher.wait()
2013-01-21 17:17:36.799 TRACE nova File "/opt/stack/
2013-01-21 17:17:36.799 TRACE nova super(ServiceLa
2013-01-21 17:17:36.799 TRACE nova File "/opt/stack/
2013-01-21 17:17:36.799 TRACE nova service.wait()
2013-01-21 17:17:36.799 TRACE nova File "/usr/local/
2013-01-21 17:17:36.799 TRACE nova return self._exit_
2013-01-21 17:17:36.799 TRACE nova File "/usr/local/
2013-01-21 17:17:36.799 TRACE nova return hubs.get_
2013-01-21 17:17:36.799 TRACE nova File "/usr/local/
2013-01-21 17:17:36.799 TRACE nova return self.greenlet.
2013-01-21 17:17:36.799 TRACE nova File "/usr/local/
2013-01-21 17:17:36.799 TRACE nova result = function(*args, **kwargs)
2013-01-21 17:17:36.799 TRACE nova File "/opt/stack/
2013-01-21 17:17:36.799 TRACE nova server.start()
2013-01-21 17:17:36.799 TRACE nova File "/opt/stack/
2013-01-21 17:17:36.799 TRACE nova self.service_id = service_ref['id']
2013-01-21 17:17:36.799 TRACE nova NameError: global name 'service_ref' is not defined
2013-01-21 17:17:36.799 TRACE nova
Corresponding to line 426 in nova/service.py: self.service_id = service_ref['id']
def start(self):
verstr = version.
ctxt = context.
try:
except exception.NotFound:
I believe this can be fixed by calling: self.service_id = self.service_
https:/
Looks like this was already a know bug and there is a patch up for review here:
https:/ /review. openstack. org/#/c/ 20120/