GitHub user insom opened a pull request:
https://github.com/apache/cloudstack/pull/1508
CLOUDSTACK-9362: Skip VXLANs when rewriting the bridge name for migrations
From the [JIRA
issue](https://issues.apache.org/jira/browse/CLOUDSTACK-9362):
>
https://github.com/apache/cloudstack/commit/bb8f7c652e42caacff5adce1ce60342603677605
>
> The above commit introduces rewriting of bridge device names when
migrating a virtual machine from one host to another. However, it also matches
bridges called "brvx-1234" and rewrites them to (in my case) "brem1-1234" -
this doesn't match the bridge name on the destination and causes the migration
to fail with the error:
>
> error : virNetDevGetMTU:397 : Cannot get interface MTU on 'brem1-1234':
No such device
>
> I have flagged this as major because it's not possible to migrate VMs
using VXLANs for maintenance, which seems important (it's certainly important
to me!).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/insom/cloudstack CLOUDSTACK-9362
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1508.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1508
----
commit bbd204c45632e1037e6c71e70593dfe10c80c4a5
Author: Aaron Brady <aa...@iweb.co.uk>
Date: 2016-04-21T14:19:56Z
Skip VXLANs when rewriting the bridge name for migrations
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
