GlusterFS volume layout: share zombies haunt forever due to overzealous delete_share
Bug #1554290 reported by
Csaba Henk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Ramana Raja |
Bug Description
GlusterFS volume layout stores the location of the backing storage of a share via private_storage.
In delete_share that location is retrieved from private_storage, from which we proceed on to the actual deallocation of the physical resource. However, this retrieval is unconditional / unguarded, so if any problem occurs with that, deletion fails. This implies that for shares for which allocation of the backing storage has failed, and thus they are in error state, cannot be cleaned away via delete_share, because they don't have a resource location stored in private_storage and so it cannot be retrieved and thus delete_share fails.
Changed in manila: | |
importance: | Undecided → Medium |
Changed in manila: | |
milestone: | none → mitaka-rc1 |
Changed in manila: | |
assignee: | Csaba Henk (chenk) → Ramana Raja (rraja) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/292177
Review: https:/