The image we this was reproduced with is cirros, which is only 12 megs in size, so the 1G volume size is appropriate. We also used a 5G volume size, with the same result. We also used a Fedora image with an 8G volume size, same result.
90% of these work just fine, about 10% of them fail with this issue, and only when there are simultaneous creates running.
Environment:
RH OSP5 (official RH) -- icehouse
host os is rhel7
iSCSI without chap
no multipathing
QCOW2 images
When we run the same exact scenario against other storage backends (we are using multiple cinder backends) this works fine, this only occurs with XtremIO.
This was initially discovered when we were teaching an end-user openstack class, where 25 people were all creating their new volumes at once. We reproduced the issue by just pasting this into the command line:
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-bbbc-4293-841b-8cb8b05ea626 5&
......
The image we this was reproduced with is cirros, which is only 12 megs in size, so the 1G volume size is appropriate. We also used a 5G volume size, with the same result. We also used a Fedora image with an 8G volume size, same result.
90% of these work just fine, about 10% of them fail with this issue, and only when there are simultaneous creates running.
Environment:
RH OSP5 (official RH) -- icehouse
host os is rhel7
iSCSI without chap
no multipathing
QCOW2 images
When we run the same exact scenario against other storage backends (we are using multiple cinder backends) this works fine, this only occurs with XtremIO.
This was initially discovered when we were teaching an end-user openstack class, where 25 people were all creating their new volumes at once. We reproduced the issue by just pasting this into the command line: bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5& bbbc-4293- 841b-8cb8b05ea6 26 5&
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
cinder create --volume-type EMC-XtremIO-1 --image-id bacd75e2-
......