After the glusterfs driver deletes the share, the client can still read and write the share
Bug #1886010 reported by
Lin PeiWen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Lin PeiWen |
Bug Description
Description
===========
Steps to reproduce
==================
* Deploying Manila using glusterfs driver
* Create a shared instance, write some unimportant data, and then delete the shared instance
Expected result
===============
Erase data in shared instance, disconnect mount point
Actual result
=============
The data in the shared instance is erased, the client mount point is not disconnected, and new data can still be read and written
Environment
===========
1.OpenStack rocky
2.Which storage backend did you use? GlusterFS driver
3.glusterfs_
4.glusterfs_
Changed in manila: | |
assignee: | nobody → Lin PeiWen (linpeiwen) |
Changed in manila: | |
status: | New → In Progress |
Changed in manila: | |
importance: | Undecided → Medium |
milestone: | none → victoria-3 |
Changed in manila: | |
assignee: | Lin PeiWen (linpeiwen) → Goutham Pacha Ravi (gouthamr) |
Changed in manila: | |
assignee: | Goutham Pacha Ravi (gouthamr) → Lin PeiWen (linpeiwen) |
To post a comment you must log in.
Additional comments http:// eavesdrop. openstack. org/meetings/ manila/ 2020/manila. 2020-08- 20-15.00. log.html