Nova requires you to name your volumev3 service cinderv3
Bug #1803627 reported by
Sam Morrison
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Matt Riedemann |
Bug Description
Nova by default looks for the cinder endpoint by looking for a service type of volumev3 and that also has a name of "cinderv3"
I think it should only be looking for an endpoint with a type of volumev3
The name attribute of an endpoint should be free to set by the operator.
In our keystone we name this "Volume API V3" which is friendly as it also appears in horizon and
using the CLI tools. (cinderv3 on the other hand is not so friendly)
Changed in nova: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Can you be more specific about where this fails, or where it's being looked up with cinderv3 hard-coded? Also, which release?
I'm aware of the volumev3 here:
https:/ /github. com/openstack/ nova/blob/ 3b2e42f37152a53 9472782ad1d71c1 f951c0343b/ nova/context. py#L130
I'm not seeing anything cinderv3 specific in here though:
https:/ /github. com/openstack/ nova/blob/ 3b2e42f37152a53 9472782ad1d71c1 f951c0343b/ nova/volume/ cinder. py
Maybe you mean this?
https:/ /github. com/openstack/ nova/blob/ c6218428e9b29a2 c52808ec7d27b4b 21aadc0299/ nova/conf/ cinder. py#L26
Which would be used here:
https:/ /github. com/openstack/ nova/blob/ 3b2e42f37152a53 9472782ad1d71c1 f951c0343b/ nova/volume/ cinder. py#L200
That is passed through to python- cinderclient, but I'm not sure if it's needed...
https:/ /github. com/openstack/ nova/blob/ 3b2e42f37152a53 9472782ad1d71c1 f951c0343b/ nova/volume/ cinder. py#L270
Maybe we should just pop it from the dict we pass to keystoneauth1 to get the endpoint URL?
https:/ /github. com/openstack/ nova/blob/ 3b2e42f37152a53 9472782ad1d71c1 f951c0343b/ nova/volume/ cinder. py#L210