Public bug reported: This bug was originally reported downstream [1][2], where a BFV server create failed due to exceeding server group member quota and leaves the volume in the "reserved" state, which prevents users from using the volume or deleting the volume.
The workaround for this is to delete the volume attachment in Cinder, which will return the volume to the "available" state. For example: $ openstack --os-volume-api-version 3.27 --os-cloud devstack volume attachment list +--------------------------------------+--------------------------------------+--------------------------------------+----------+ | ID | Volume ID | Server ID | Status | +--------------------------------------+--------------------------------------+--------------------------------------+----------+ | d4470d80-ec1d-480c-8c59-1b3ff2f3985f | a4ef4a82-6aad-4637-8759-e01bb706ef2f | c6e2f02e-a408-4a5f-a325-55481a7d5c61 | reserved | +--------------------------------------+--------------------------------------+--------------------------------------+----------+ $ openstack --os-volume-api-version 3.27 --os-cloud devstack volume attachment delete d4470d80-ec1d-480c-8c59-1b3ff2f3985f After that the volume should be in 'available' state and able to be deleted. To fix the bug, we will need to have Nova delete the "reserved" volume attachment if quota is exceeded for server group members. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2279757 [2] https://issues.redhat.com/browse/OSPRH-13121 ** Affects: nova Importance: Undecided Status: New ** Tags: low-hanging-fruit volumes ** Tags added: low-hanging-fruit -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/2096884 Title: Server create request leaves volume in reserved state when server group quota is exceeded Status in OpenStack Compute (nova): New Bug description: This bug was originally reported downstream [1][2], where a BFV server create failed due to exceeding server group member quota and leaves the volume in the "reserved" state, which prevents users from using the volume or deleting the volume. The workaround for this is to delete the volume attachment in Cinder, which will return the volume to the "available" state. For example: $ openstack --os-volume-api-version 3.27 --os-cloud devstack volume attachment list +--------------------------------------+--------------------------------------+--------------------------------------+----------+ | ID | Volume ID | Server ID | Status | +--------------------------------------+--------------------------------------+--------------------------------------+----------+ | d4470d80-ec1d-480c-8c59-1b3ff2f3985f | a4ef4a82-6aad-4637-8759-e01bb706ef2f | c6e2f02e-a408-4a5f-a325-55481a7d5c61 | reserved | +--------------------------------------+--------------------------------------+--------------------------------------+----------+ $ openstack --os-volume-api-version 3.27 --os-cloud devstack volume attachment delete d4470d80-ec1d-480c-8c59-1b3ff2f3985f After that the volume should be in 'available' state and able to be deleted. To fix the bug, we will need to have Nova delete the "reserved" volume attachment if quota is exceeded for server group members. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2279757 [2] https://issues.redhat.com/browse/OSPRH-13121 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2096884/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
