AttributeError: display_name when changing cinder endpoint to v2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Undecided
|
Unassigned |
Bug Description
cinder endpoint v2 changed the volume names attr to --name instead of --display-name.
when I change the cinder endpoint to v2 and create volumes, horizon crashes when we try to query the volumes:
2013-11-28 13:26:10,862 24349 ERROR django.request Internal Server Error: /dashboard/
Traceback (most recent call last):
File "/usr/lib/
response = callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/
return view_func(request, *args, **kwargs)
File "/usr/lib/
return view_func(request, *args, **kwargs)
File "/usr/lib/
return view_func(request, *args, **kwargs)
File "/usr/lib/
return view_func(request, *args, **kwargs)
File "/usr/lib/
return self.dispatch(
File "/usr/lib/
return handler(request, *args, **kwargs)
File "/usr/lib/
handled = self.construct_
File "/usr/lib/
handled = self.handle_
File "/usr/lib/
data = self._get_
File "/usr/lib/
self._data = {self.table_
File "/usr/share/
self.
File "/usr/share/
if not volume.
File "/usr/lib/
raise AttributeError(k)
AttributeError: display_name
to reproduce:
Run the following in cli:
1. install openstack with packstack
2. change cinder's endpoint in keystone to v2:
keystone endpoint-create --region RegionOne --service-id 10fd33fdca4f4ca
delete the old v1 endpoint:
keystone endpoint-delete <endpoint that uses v1>
3. create a volume using v2 API:
OS_VOLUME_
4. log in to horizon -> project -> volumes
result:
Horizon gives an attr error on name
David Taylor (dtaylor-z) wrote : | #1 |
Napo Mokoetle (azanians) wrote : | #2 |
I've also been experiencing this exact same problem with attaching volumes to virtual instances. When I try to attach a volume with the following command:
=============+
root@ts036953:
ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-008288f6-
=============+
And then when I try to attach to device that the instance already has I get the following message. Which kind of indicates that the instance is a least getting touched by the "nova volume-attach" command. What logs can I look into to see more detailed messages on what could be going wrong during this volume-attach attempt?
=============+
root@ts036953:
ERROR: The supplied device path (/dev/vda) is in use. (HTTP 409) (Request-ID: req-83c8afe9-
=============+
Julie Pichon (jpichon) wrote : | #3 |
You might be interested in bug 1215772, Nova doesn't support Cinder v2 yet.
I am experiencing this same issue. Whenever I try to access the Volumes tab in Horizon I get the same error message as above.
Cinder Version: 1.0.7