server migration across physical networks

Bug #2002019 reported by chuan137
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
In Progress

Bug Description


I am using the server migration feature to migrate share servers from one host to another keeping the same share network. Current implementation assumes that the network on source and target host are in the same network segment, i.e. segmentation id is not changed. However, in our environments, the backend hosts may be connected to different physical networks. So the neutron networks consist of multiple segments, with different segmentation ids. Thus migration fails.

Steps to reproduce

1. manila share-server-migration-check --preserve-snapshots True --writable True --nondisruptive True a85f022b-cddd-40bf-b95f-bfa84d64868c manila-share-netapp-ma01-md004@ma01-md004

Expected result
compatible: True

Actual result
compatible: False

Manila: Xena
Storage: NetApp (dhss=True)
   type_drivers = vlan,vxlan
   tenant_network_types = vxlan,vlan

Best regards,

chuan137 (chuan137)
description: updated
Changed in manila:
assignee: nobody → chuan137 (chuan137)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master

Changed in manila:
status: New → In Progress
Revision history for this message
Maurice Escher (maurice-escher) wrote :

The required neutron enhancement is in

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on manila (master)

Change abandoned by "Chuan Miao <email address hidden>" on branch: master

Revision history for this message
Vida Haririan (vhariria) wrote :

See related comments in manila-dalmatian-m2-bugsquash ethercal

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.