cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9362) Migrating a VM using VXLANs and bridges fails
Date Fri, 22 Apr 2016 13:41:12 GMT

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

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

Github user insom commented on the pull request:

    https://github.com/apache/cloudstack/pull/1508#issuecomment-213431813
  
    @swill Thanks! Should I rebase this against the latest 4.8 branch then? I don't think
I can change where a PR is based against, so I think I'd need to open a new PR - is that right
call?


> 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)

Mime
View raw message