Wrong segmentation ID sent to drivers when using multi-segments

Bug #1799742 reported by Rodrigo Barbieri on 2018-10-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Manila
Medium
Sneha Prasad

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://github.com/openstack/manila/blob/2b40e5618f2c1039bbbbd1a3e31b72e104b5436b/manila/network/neutron/neutron_network_plugin.py#L270 where it iterates across all segments and the last one is the one that is used.

Adding a LOG.debug(str(network_info)) before invoking the driver's setup_server also shows the wrong segmentation ID is passed down to the driver.

Changed in manila:
importance: Undecided → Medium
Sneha Prasad (snpd) wrote :

I would like to work on this issue, what is the expected change in the code?

Sneha Prasad (snpd) on 2019-03-21
Changed in manila:
assignee: nobody → Sneha Prasad (snpd)
Jason Grosso (jgrosso) on 2019-03-22
Changed in manila:
status: New → Triaged

Fix proposed to branch: master
Review: https://review.openstack.org/648755

Changed in manila:
status: Triaged → In Progress
Jason Grosso (jgrosso) wrote :

Sneha is there any update to this bug?

Sneha Prasad (snpd) wrote :

Jason, I am not sure what is the change required here. Should segmentation_id be a list so that all the segment IDs will be appended to it or any other modification is required. It will be helpful if I receive a suggestion on this.

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

Other bug subscribers