[NetApp driver] Vserver deletion tries to acquire lock when it is already locked
Bug #1831092 reported by
Carlos Eduardo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Low
|
Douglas Viroel |
Bug Description
When creating and deleting servers, NetApp driver needs to lock a resource for itself.
NetApp driver is having some troubles when it needs to delete some server resources during the server creation. When the driver starts to create a new server and this operation fails, an automatic proccess, that clean all the resources created untill that moment is started. When the deletion is about to start, the removal operation tries to lock a resource that was already locked by the creation proccess, then, the deletion operation will starve.
When the server creation operation fails, the NetApp driver should not try to lock a locked resource.
tags: | added: netapp |
Changed in manila: | |
assignee: | nobody → Douglas Viroel (dviroel) |
Changed in manila: | |
importance: | Undecided → Low |
milestone: | none → train-2 |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/662889
Review: https:/