You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Jessica Tomechak (JIRA)" <ji...@apache.org> on 2013/10/04 19:57:44 UTC
[jira] [Updated] (CLOUDSTACK-4550) [DOC] When upgrading KVM agents
to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jessica Tomechak updated CLOUDSTACK-4550:
-----------------------------------------
Assignee: (was: Jessica Tomechak)
> [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
>
> 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)