cinderclient AmbiguousEndpoints in Nova API when deleting nested stack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
python-cinderclient |
Invalid
|
Undecided
|
Unassigned |
Bug Description
While chasing down some errors I found the first one was the following, found in the log from the Nova API process.
2014-03-06 22:17:41.713 ERROR nova.api.openstack [req-0a2e7b6b-
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack Traceback (most recent call last):
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return req.get_
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack application, catch_exc_
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack app_iter = application(
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return resp(environ, start_response)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return self.app(env, start_response)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return resp(environ, start_response)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return resp(environ, start_response)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack response = self.app(environ, start_response)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return resp(environ, start_response)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack resp = self.call_func(req, *args, **self.kwargs)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/usr/lib/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return self.func(req, *args, **kwargs)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack content_type, body, accept)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack action_result = self.dispatch(meth, request, action_args)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack return method(req=request, **action_args)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack volume = self.volume_
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack res = method(self, ctx, volume_id, *args, **kwargs)
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack item = cinderclient(
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack endpoint_
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack File "/opt/stack/
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack endpoints=
2014-03-06 22:17:41.713 17339 TRACE nova.api.openstack AmbiguousEndpoints: AmbiguousEndpoints: [{u'url': u'http://
This is reminiscent of bug 1154809 --- which was fixed a year ago.
My scenario is as follows. I started with a fresh DevStack install around 04:00 on March 5, 2013 UTC. Heat Orchestration Template VM_with_EBS.yaml has three resources: a VM instance, a volume, and an attachment between the two. HOT ASRG2.yaml has several resources, one of which is an OS::Heat:
I am attaching VM_with_EBS.yaml with the initial bug report; I will attach ASRG2.yaml when I figure out how to do so.
Seems like devstack doesn't configure keystone in a way that heat recognises