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

hayou commented on CLOUDSTACK-4550:
-----------------------------------

not really Wei Zhou ;).
I have the same error on my management : 
{quote}
2013-11-06 16:02:15,989 ERROR [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-163:job-399 = [ a47926cf-d712-4bc1-926b-3a8ac43d9e40 ]) Unable to 
migrate due to Cannot get interface MTU on 'brbond0.110-110': No such device
{quote}

I type  /usr/bin/cloudstack-agent-upgrade on my 2 hypervisors then reboot.


Here is my agent properties  : 
{quote}
guest.network.device=cloudVirBr100
workers=5
private.network.device=cloudVirBr100
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
network.bridge.name.schema=3.0
zone=1
guid=8b928279-d5af-30a9-bc27-6e872a065372
cluster=1
public.network.device=cloudVirBrPub
local.storage.uuid=9342a19c-7822-4a4b-9e83-543742528a81
domr.scripts.dir=scripts/network/domr/kvm
host=172.....
LibvirtComputingResource.id=4
{quote}

> [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have 
> migration work
> ------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4550
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc, KVM, Upgrade
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Priority: Critical
>         Attachments: bridge.jpg
>
>
> See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as
> part of upgrade in release notes once the fix for the bug is verified to work
> After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN to 
> support the same VLAN on multiple physical networks the migration of VMs from 
> hosts prior the upgrade to the ones added after the upgrade will fail. 
> In order to fix this rename the bridges is required to allow migration to 
> work.
> This can be done by running the cloudstack-agent-upgrade script. The original 
> bug is still undergoing testing, but these are the initial instructions



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to