PV VG Fmt Attr PSize PFree
/dev/sda5 VolGroup00 lvm2 a-- 687,78g 651,78g
/dev/sdb cinder-volumes lvm2 a-- 931,51g 931,51g
/dev/sdc cinder-volumes lvm2 a-- 931,51g 931,51g
/dev/sdd cinder-volumes lvm2 a-- 698,63g 698,63g
/dev/sde cinder-volumes lvm2 a-- 931,51g 931,51g
/dev/sdf cinder-volumes lvm2 a-- 931,51g 931,51g
vgs
VG #PV #LV #SN Attr VSize VFree
VolGroup00 1 5 0 wz--n- 687,78g 651,78g
cinder-volumes 5 0 0 wz--n- 4,32t 4,32t
When running the create command no logical volume is created. (I am, manually, able to create a 5G lv in the vg cinder-volumes)
root@OpenStackNode2 /var/log/cinder$ cinder list
+--------------------------------------+----------+--------------+------+-------------+-------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+--------------------------------------+----------+--------------+------+-------------+-------------+
| 43500252-845d-41c8-bf65-ab65650863f6 | creating | test-volume | 5 | None | |
+--------------------------------------+----------+--------------+------+-------------+-------------+
Output of the create command with the debug turn on :
root@OpenStackNode2 /var/log/cinder$ cinder --debug create 1
connect: (172.16.41.166, 35357) ***
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 172.16.41.166:35357\r\nContent-Length: 101\r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-cinderclient\r\n\r\n'
send: '{"auth": {"tenantName": "demo", "passwordCredentials": {"username": "admin", "password": ""}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Vary: X-Auth-Token
header: Content-Type: application/json
header: Content-Length: 2749
header: Date: Tue, 05 Mar 2013 10:34:44 GMT
connect: (172.16.41.168, 8776) *****
send: u'POST /v1/26568729f86f4bb18359fc800ef207c3/volumes HTTP/1.1\r\nHost: 172.16.41.168:8776\r\nContent-Length: 265\r\nx-auth-project-id: demo\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nx-auth-token: 46bf3196b5b946879022d147e31d9f5a\r\nuser-agent: python-cinderclient\r\ncontent-type: application/json\r\n\r\n'
send: '{"volume": {"status": "creating", "availability_zone": null, "display_description": null, "snapshot_id": null, "user_id": null, "size": 1, "display_name": null, "imageRef": null, "attach_status": "detached", "volume_type": null, "project_id": null, "metadata": {}}}'
Some extra information, my scheduler.log remains untouched. Only when I restart the cinder-scheduler service is sees some activity
fyi : the behavior remains the same when I use the python-novaclient instead of the python-cinderclient : "nova volume-create --display_name vol0 10"