Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 17 May 2016 09:18:12 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12960765.1461248752000.207876.1463476692837@Atlassian.JIRA>
In-Reply-To: <JIRA.12960765.1461248752000@Atlassian.JIRA>
References: <JIRA.12960765.1461248752000@Atlassian.JIRA> <JIRA.12960765.1461248752875@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9362) Migrating a VM using VXLANs
 and bridges fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 17 May 2016 09:18:14 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286273#comment-15286273 ] 

ASF GitHub Bot commented on CLOUDSTACK-9362:
--------------------------------------------

Github user insom commented on the pull request:

    https://github.com/apache/cloudstack/pull/1513#issuecomment-219663341
  
    @swill rebased and pushed. It does have two LGTMs and tests by real people (plus it's in production at here at iWeb) if that makes it a little easier to overrule Jenkins.


> Migrating a VM using VXLANs and bridges fails
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-9362
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9362
>             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
>
> 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!).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)