Wrong segmentation ID sent to drivers when using multi-segments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Invalid
|
Low
|
Unassigned |
Bug Description
When using multi-segments in neutron, if we create a subnet for each segment and a share network for each subnet, when creating shares in DHSS=True mode, the driver receives the same segmentation ID for all share networks, instead of receiving the proper one for each.
Steps to reproduce:
1) Create neutron net
2) Create 3 VLAN segments (350, 360 and 370)
3) Create 3 Subnets, 1 for each segment
4) Create 3 Share Networks, 1 for each subnet
5) Create a share on each of the share networks.
6) Display the details of the share networks, they will all have the same segmentation ID (either 350, 360 or 370) instead of 1 for each
The problem is in https:/
Adding a LOG.debug(
Changed in manila: | |
importance: | Undecided → Medium |
Changed in manila: | |
assignee: | nobody → Sneha Prasad (snpd) |
Changed in manila: | |
status: | New → Triaged |
I would like to work on this issue, what is the expected change in the code?