cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-4405) (Upgrade) Migrate failed between existing hosts and new hosts
Date Thu, 05 Sep 2013 12:34:51 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wei Zhou reopened CLOUDSTACK-4405:
----------------------------------


There still exist two issues
(1) Migration from new hosts to old hosts failed.
as the bridge name on old host is set to cloudVirBr* if network.bridge.name.schema is set
to 3.0 in /etc/cloudstack/agent/agent.properties, but the actual bridge name is breth*-* after
running cloudstack-agent-upgrade.

(2) all ports of vms (Basic zone, or Advanced zone with security groups) on old hosts are
open, because the iptables rules are binding to device (bridge) name which is changed by cloudstack-agent-upgrade.

I posted a patch for these two issues. It is tested ok on my environment.
https://reviews.apache.org/r/13992/

After this, the KVM upgrade steps :
a. Install 4.2 cloudstack agent on each kvm host 
b. Run "cloudstack-agent-upgrade". This script will upgrade all the existing bridge name to
new bridge name, and update related firewall rules.
       c. install a libvirt hook:
            c1. mkdir /etc/libvirt/hooks
            c2. cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu
            c3. chmod +x /etc/libvirt/hooks/qemu
            c4. service libvirtd restart
            c5. service cloudstack-agent restart
                
> (Upgrade) Migrate failed between existing hosts and new hosts
> -------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4405
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4405
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0, 4.2.0
>         Environment: CS 4.1
>            Reporter: Wei Zhou
>            Assignee: edison su
>            Priority: Blocker
>              Labels: ReleaseNote
>             Fix For: 4.1.1, 4.2.0, 4.2.1
>
>
> There are two hosts (cs-kvm001, cs-kvm002) in old 2.2.14 environment .
> After upgrade from 2.2.14 to 4.1, I added two new hosts (cs-kvm003, cs-kvm004).
> The migration between cs-kvm001 and cs-kvm002, or cs-kvm003 and cs-kvm004 succeed.
> However, the migration from cs-kvm001/002 to the new hosts (cs-kvm003, cs-kvm004) failed.
> 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-1:null)
nic=[Nic:Guest-10.11.110.231-vlan://110]
> 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-1:null)
creating a vlan dev and bridge for guest traffic per traffic label cloudbr0
> 2013-08-19 16:57:31,051 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Executing:
/bin/bash -c brctl show | grep cloudVirBr110
> 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Exit
value is 1
> 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] (agentRequest-Handler-1:null)
> 2013-08-19 16:57:31,063 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-1:null)
Executing: /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 110 -p em1
-b brem1-110 -o add
> 2013-08-19 16:57:31,121 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-1:null)
Execution is successful.
> 2013-08-19 16:57:31,122 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-1:null)
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
> This is because the bridge name on old hosts are cloudVirBr110, and brem1-110 on new
hosts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message