share server cleanup removes connectivity (generic driver)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Valeriy Ponomaryov | ||
Kilo |
Fix Released
|
Medium
|
Valeriy Ponomaryov |
Bug Description
Steps to recreate the bug:
Environment: default devstack + manila.
1. Create a Share Network "share_net_1" using "private" network and "private-subnet" subnetwork.
2. Create a Share Network "share_net_2" using "private" network and "private-subnet" subnetwork.
3. Create a Share "share_1" specifying "share_net_1", wait for available status.
4. Create a Share "share_2" specifying "share_net_2", wait for available status.
At this point, two Share Servers are being created on the same Manila Subnetwork 10.254.0.0/28. It will add an interface to "router1" that connects it to Manila Subnetwork, the IP address should be 10.254.0.1.
5. Delete "share_2".
6. Wait for Share server cleanup.
7. Check for network interface "10.254.0.1" in "router1", it has been removed and "share_1" cannot be mounted from any VM in "private" network.
tags: | added: driver generic |
tags: | added: kilo-backport-potential |
Changed in manila: | |
assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
status: | New → In Progress |
milestone: | none → liberty-1 |
Changed in manila: | |
importance: | Undecided → Medium |
Changed in manila: | |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | liberty-1 → 1.0.0 |
Changed in manila: | |
milestone: | 1.0.0 → none |
Fix proposed to branch: master /review. openstack. org/181380
Review: https:/