cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kishan Kavala (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-5322) CreateNetwork command doesnt fails on non upgraded vpc router
Date Wed, 11 Dec 2013 09:49:07 GMT


Kishan Kavala resolved CLOUDSTACK-5322.

    Resolution: Fixed

Adding new tier, creates a new network in Allocated state. It is not still implemented and
no commands are sent to VR.
When a new Vm is created in this tier, network is implemented and commands are sent to VR.

When VR is at older version, new Vm creation fails which is the expected behaviour.

Failure logs:
2013-12-11 15:10:13,204 DEBUG [c.c.a.t.Request] (Job-Executor-6:ctx-73163d21 ctx-a4c9b5ae)
Seq 1-1862336579: Received:  { Ans: , MgmtId: 101318455136477, via: 1, Ver: v1, Flags: 110,
{ PlugNicAnswer } }
2013-12-11 15:10:13,205 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-6:ctx-73163d21
ctx-a4c9b5ae) Nic is plugged successfully for vm VM[DomainRouter|r-6-VM] in network Ntwk[206|Guest|11].
Vm  is a part of network now
2013-12-11 15:10:13,273 DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-6:ctx-73163d21 ctx-a4c9b5ae)
Service SecurityGroup is not supported in the network id=206
2013-12-11 15:10:13,282 WARN  [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] (Job-Executor-6:ctx-73163d21
ctx-a4c9b5ae) Failed to add router VM[DomainRouter|r-6-VM] to network Ntwk[206|Guest|11] due
to Router requires upgrade. Unable to send command
to router:6

> CreateNetwork command doesnt fails on non upgraded  vpc router
> --------------------------------------------------------------
>                 Key: CLOUDSTACK-5322
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade, Virtual Router
>    Affects Versions: 4.3.0
>            Reporter: shweta agarwal
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.3.0
> Repro steps:
> On 3.0.7 setup create a vpc network and some vms in that network
> Upgrade to 4.3
> while router is still in old version template create a new tire in VPC network
> bug:
> New Tier is created without any failure
> Expected result:
> We should not let new tire creation till router of the VPC network is upgraded
> this in turn is creating further problems
>  1. able to create  a new VM withing this new tier even though router is not upgraded
>  2. able to create a new PF rule /LB rule within this new tier without failure
> so to block all these issue we should block creation of new tier itself inside a VPC
network if its router is not upgraded.
> API call 

This message was sent by Atlassian JIRA

View raw message