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 Thu, 21 Apr 2016 14:29:25 GMT

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

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

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 <aaron@iweb.co.uk>
Date:   2016-04-21T14:19:56Z

    Skip VXLANs when rewriting the bridge name for migrations

----


> 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