Deadlock occurs when share server create is called but fails

Bug #1706092 reported by chad morgenstern on 2017-07-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Manila
Low
Unassigned

Bug Description

When using share servers in manila, and when the share server is created, if manila attempts to create the share server but fails to complete the process, the process is left in creating state rather than error or completed. Further, manila creates the share object.

In this state, neither the share server nor the share object can be deleted from manila. To work around the issue, presently, one has to enter the database and change the state of the share server from creating to a final state.

This issue is occuring because of lock contention.

chad morgenstern (mchad) wrote :

[root@chadcloud1 network-scripts(keystone_admin)]# manila list
+--------------------------------------+------+------+-------------+----------+-----------+-----------------+-------------------------------------------+-------------------+
| ID | Name | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
+--------------------------------------+------+------+-------------+----------+-----------+-----------------+-------------------------------------------+-------------------+
| f10b9908-d662-4454-9d65-a0fb0c2b6bac | None | 1 | NFS | creating | False | multi | chadcloud1@cdot_multi#openstack1_sas_aggr | nova |
+--------------------------------------+------+------+-------------+----------+-----------+-----------------+-------------------------------------------+-------------------+

tags: added: drivers netapp vendor
Changed in manila:
status: New → Confirmed
importance: Undecided → Low
Tom Barron (tpb) on 2018-06-19
tags: added: driver
removed: drivers
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers