| 2021-08-18 18:22:41 |
Mitya Eremeev |
bug |
|
|
added bug |
| 2021-08-18 18:25:23 |
Mitya Eremeev |
cinder: assignee |
|
Mitya Eremeev (mitos) |
|
| 2021-08-18 18:25:52 |
Mitya Eremeev |
cinder: status |
New |
In Progress |
|
| 2021-08-18 18:31:50 |
Mitya Eremeev |
description |
1. launch two commands one after another and don’t wait responses (in 2 terminal tabs)
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_1
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_2
2.see volumes statuses
$ openstack volume list
+--------------------------------------+----------+-----------+------+-------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------+-----------+------+-------------+
| f1cbfc3c-263b-48fd-8ef0-5ad06d2e99ba | volume_2 | error | 50 | |
| 5bbb5dab-c001-4c19-a61d-f1e7f8be8170 | volume_1 | available | 50 | |
+--------------------------------------+----------+-----------+------+-------------+
3. see cinder logs
ERROR cinder.volume.api [req-41b9c765-827d-4c75-ac95-331c8fa0c840 cd15c27229234675ac78f3f83af1c60c 3a2aec7e5c5b46c2a366e471fa133066 - 3f2f1264e29e4cc9913aa2a63197866a 3f2f1264e29e4cc9913aa2a63197866a] Volume status must be available or in-use to reserve, but the status is attaching.
expected behavior:
two volumes created successfully
actual behavior:
the second volume was not created because the first volume creation task reserved volume.
I suggest to implement retry mechanism in order to be able to wait volume to become available. |
1. launch two commands one after another and don’t wait responses (in 2 terminal tabs)
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_1
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_2
2.see volumes statuses
$ openstack volume list
+--------------------------------------+----------+-----------+------+-------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------+-----------+------+-------------+
| f1cbfc3c-263b-48fd-8ef0-5ad06d2e99ba | volume_2 | error | 50 | |
| 5bbb5dab-c001-4c19-a61d-f1e7f8be8170 | volume_1 | available | 50 | |
+--------------------------------------+----------+-----------+------+-------------+
3. see cinder logs
ERROR cinder.volume.api [req-41b9c765-827d-4c75-ac95-331c8fa0c840 cd15c27229234675ac78f3f83af1c60c 3a2aec7e5c5b46c2a366e471fa133066 - 3f2f1264e29e4cc9913aa2a63197866a 3f2f1264e29e4cc9913aa2a63197866a] Volume status must be available or in-use to reserve, but the status is attaching.
expected behavior:
two volumes created successfully
actual behavior:
the second volume was not created because the first volume creation task reserved volume.
Bug in RHOSP: https://bugzilla.redhat.com/show_bug.cgi?id=1886013
I suggest to implement retry mechanism in order to be able to wait volume to become available. |
|
| 2021-08-19 17:26:33 |
Mitya Eremeev |
summary |
Simultaneous volume creation with the same image returns error "Volume status must be available or in-use to reserve, but the status is attaching" |
Simultaneous volume creation with the same image in multiattach mode returns error "Volume status must be available or in-use to reserve, but the status is attaching" |
|
| 2021-08-20 15:12:26 |
Sofia Enriquez |
tags |
|
attach glance glance-store image multiattach volume |
|
| 2021-08-20 15:12:34 |
Sofia Enriquez |
cinder: importance |
Undecided |
Wishlist |
|
| 2021-09-02 19:32:48 |
Mitya Eremeev |
summary |
Simultaneous volume creation with the same image in multiattach mode returns error "Volume status must be available or in-use to reserve, but the status is attaching" |
Simultaneous volume creation with the same image in multi-attach mode returns error. |
|
| 2021-09-02 19:35:25 |
Mitya Eremeev |
description |
1. launch two commands one after another and don’t wait responses (in 2 terminal tabs)
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_1
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_2
2.see volumes statuses
$ openstack volume list
+--------------------------------------+----------+-----------+------+-------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------+-----------+------+-------------+
| f1cbfc3c-263b-48fd-8ef0-5ad06d2e99ba | volume_2 | error | 50 | |
| 5bbb5dab-c001-4c19-a61d-f1e7f8be8170 | volume_1 | available | 50 | |
+--------------------------------------+----------+-----------+------+-------------+
3. see cinder logs
ERROR cinder.volume.api [req-41b9c765-827d-4c75-ac95-331c8fa0c840 cd15c27229234675ac78f3f83af1c60c 3a2aec7e5c5b46c2a366e471fa133066 - 3f2f1264e29e4cc9913aa2a63197866a 3f2f1264e29e4cc9913aa2a63197866a] Volume status must be available or in-use to reserve, but the status is attaching.
expected behavior:
two volumes created successfully
actual behavior:
the second volume was not created because the first volume creation task reserved volume.
Bug in RHOSP: https://bugzilla.redhat.com/show_bug.cgi?id=1886013
I suggest to implement retry mechanism in order to be able to wait volume to become available. |
1. launch two commands one after another and don’t wait responses (in 2 terminal tabs)
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_1
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_2
2.see volumes statuses
$ openstack volume list
+--------------------------------------+----------+-----------+------+-------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------+-----------+------+-------------+
| f1cbfc3c-263b-48fd-8ef0-5ad06d2e99ba | volume_2 | error | 50 | |
| 5bbb5dab-c001-4c19-a61d-f1e7f8be8170 | volume_1 | available | 50 | |
+--------------------------------------+----------+-----------+------+-------------+
3. see cinder logs
ERROR cinder.volume.api [req-41b9c765-827d-4c75-ac95-331c8fa0c840 cd15c27229234675ac78f3f83af1c60c 3a2aec7e5c5b46c2a366e471fa133066 - 3f2f1264e29e4cc9913aa2a63197866a 3f2f1264e29e4cc9913aa2a63197866a] Volume status must be available or in-use to reserve, but the status is attaching.
or similar error message, but the status in detaching.
expected behavior:
two volumes created successfully
actual behavior:
the second volume was not created because the first volume creation task reserved volume.
Bug in RHOSP: https://bugzilla.redhat.com/show_bug.cgi?id=1886013 |
|
| 2021-09-02 19:37:20 |
Mitya Eremeev |
description |
1. launch two commands one after another and don’t wait responses (in 2 terminal tabs)
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_1
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_2
2.see volumes statuses
$ openstack volume list
+--------------------------------------+----------+-----------+------+-------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------+-----------+------+-------------+
| f1cbfc3c-263b-48fd-8ef0-5ad06d2e99ba | volume_2 | error | 50 | |
| 5bbb5dab-c001-4c19-a61d-f1e7f8be8170 | volume_1 | available | 50 | |
+--------------------------------------+----------+-----------+------+-------------+
3. see cinder logs
ERROR cinder.volume.api [req-41b9c765-827d-4c75-ac95-331c8fa0c840 cd15c27229234675ac78f3f83af1c60c 3a2aec7e5c5b46c2a366e471fa133066 - 3f2f1264e29e4cc9913aa2a63197866a 3f2f1264e29e4cc9913aa2a63197866a] Volume status must be available or in-use to reserve, but the status is attaching.
or similar error message, but the status in detaching.
expected behavior:
two volumes created successfully
actual behavior:
the second volume was not created because the first volume creation task reserved volume.
Bug in RHOSP: https://bugzilla.redhat.com/show_bug.cgi?id=1886013 |
environment:
Glance backend is Cinder.
Multi-attachment is enabled.
1. launch two commands one after another and don’t wait responses (in 2 terminal tabs)
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_1
$ openstack volume create --size 50 --image Ubuntu-18.04 volume_2
2.see volumes statuses
$ openstack volume list
+--------------------------------------+----------+-----------+------+-------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------+-----------+------+-------------+
| f1cbfc3c-263b-48fd-8ef0-5ad06d2e99ba | volume_2 | error | 50 | |
| 5bbb5dab-c001-4c19-a61d-f1e7f8be8170 | volume_1 | available | 50 | |
+--------------------------------------+----------+-----------+------+-------------+
3. see cinder logs
ERROR cinder.volume.api [req-41b9c765-827d-4c75-ac95-331c8fa0c840 cd15c27229234675ac78f3f83af1c60c 3a2aec7e5c5b46c2a366e471fa133066 - 3f2f1264e29e4cc9913aa2a63197866a 3f2f1264e29e4cc9913aa2a63197866a] Volume status must be available or in-use to reserve, but the status is attaching.
or similar error message, but the status in detaching.
expected behavior:
two volumes created successfully
actual behavior:
the second volume was not created because the first volume creation task reserved volume.
Bug in RHOSP: https://bugzilla.redhat.com/show_bug.cgi?id=1886013 |
|
| 2022-04-07 09:25:24 |
Bence Romsics |
attachment added |
|
paste https://bugs.launchpad.net/cinder/+bug/1940466/+attachment/5577857/+files/paste |
|
| 2022-04-28 18:44:40 |
Sofia Enriquez |
tags |
attach glance glance-store image multiattach volume |
attach documentation glance glance-store image multiattach volume |
|
