Launch instance from image (as new volume) fails when giving different size to volume (NoneType' object has no attribute 'update_volume_group_info)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I tried running a new instance from image (create new volume)
if device size remains 1 we can launch the instance and create the volume.
but if I change the device size to 30 we fail creating the volume with the following error:
2013-09-25 17:31:16.469 27155 ERROR cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-09-25 17:31:16.469 27155 TRACE cinder.
2013-10-02 13:56:08.968 8386 ERROR cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:08.968 8386 TRACE cinder.
2013-10-02 13:56:09.964 8386 ERROR cinder.
2013-10-02 13:56:09.964 8386 ERROR cinder.service [req-c86406a3-
2013-10-02 13:56:09.964 8386 TRACE cinder.service Traceback (most recent call last):
2013-10-02 13:56:09.964 8386 TRACE cinder.service File "/usr/lib/
2013-10-02 13:56:09.964 8386 TRACE cinder.service self._child_
2013-10-02 13:56:09.964 8386 TRACE cinder.service File "/usr/lib/
2013-10-02 13:56:09.964 8386 TRACE cinder.service launcher.
2013-10-02 13:56:09.964 8386 TRACE cinder.service File "/usr/lib/
2013-10-02 13:56:09.964 8386 TRACE cinder.service server.start()
2013-10-02 13:56:09.964 8386 TRACE cinder.service File "/usr/lib/
2013-10-02 13:56:09.964 8386 TRACE cinder.service self.manager.
2013-10-02 13:56:09.964 8386 TRACE cinder.service File "/usr/lib/
2013-10-02 13:56:09.964 8386 TRACE cinder.service self.driver.
2013-10-02 13:56:09.964 8386 TRACE cinder.service File "/usr/lib/
2013-10-02 13:56:09.964 8386 TRACE cinder.service raise exception.
2013-10-02 13:56:09.964 8386 TRACE cinder.service VolumeBackendAP
2013-10-02 13:56:09.964 8386 TRACE cinder.service
I know its an attribute issue but just in case someone asks...
[root@nott-vdsa images(
VG #PV #LV #SN Attr VSize VFree
cinder-volumes 1 1 0 wz--n- 3.19g 2.19g
vg0 1 2 0 wz--n- 232.69g 0
summary: |
- lauch instance from image (as new volume) fails when giving different + Launch instance from image (as new volume) fails when giving different size to volume (NoneType' object has no attribute 'update_volume_group_info) |
Strange, according to this the second time your ran the command the vg member object of your volume driver was not intialized.
Can you please list the commands and steps you performed that lead to this?
If you just did:
'cinder create --image-id xxxx 1'
Followed by:
'cinder create --image-id xxxx 30'
I don't see how this is possible, unless you have multiple backend drivers configured, or there were some other operations inbetween there that you performed.