gluster driver volume layout self.gluster_used_vols collection record is inaccurate

Bug #1922176 reported by Lin PeiWen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
New
Undecided
Unassigned

Bug Description

Deploy multiple gluster-driven share services, use volume layout, create and delete share instances multiple times,

It is found that the parameters in the self.gluster_used_vols collection variable in the three node services do not correspond to the records in the self.private_storage database.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.