NFS share with generic driver doesn't survive a service VM reboot
Bug #1358688 reported by
Thomas Bechtold
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
Valeriy Ponomaryov |
Bug Description
I created a NFS share with the generic driver and created one access-list entry. After rebooting the Manila service VM, the share is no longer exported.
Steps to reproduce:
- Create a Manila share with "manila create"
- Create a access-list entry with "manila access-allow". The access entry is now in state "active" and on the Manila share VM, there should be an entry in"showmount -e"
- Reboot service VM with "nova restart"
- The share is gone (no output on "showmount -e") but "manila access-list" still shows that there is an entry in "active" state
Changed in manila: | |
importance: | Undecided → High |
assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
status: | New → In Progress |
Changed in manila: | |
milestone: | none → juno-rc1 |
Changed in manila: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It depends on image, does it save its state or not. Restart of m-shr service retries all active rules. But I agree, that this should be handled somehow.
Maybe, we can implement some periodic tast with check of availability of VM, and if it was not available for some time, then try to reassign all rules when it becomes available.