cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9362) Migrating a VM using VXLANs and bridges fails
Date Mon, 16 May 2016 20:27:12 GMT


ASF GitHub Bot commented on CLOUDSTACK-9362:

Github user swill commented on the pull request:
    @insom we are down to the wire here.  I would like to see if we can get this green and
merge it before the freeze.  Can you rebase and push again to kick the automation.  I will
likely make judgement calls and merge PRs that have a passing travis even if jenkins is failing.
 We will see.  I would rather not be in that situation...

> Migrating a VM using VXLANs and bridges fails
> ---------------------------------------------
>                 Key: CLOUDSTACK-9362
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.6.2, 4.7.1, 4.8.0
>         Environment: Using KVM with VXLANs in Linux bridge devices (not OpenVSwitch)
>            Reporter: Aaron Brady
> 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!).

This message was sent by Atlassian JIRA

View raw message