You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/12/10 19:28:08 UTC
[jira] [Reopened] (CLOUDSTACK-5322) CreateNetwork command doesnt
fails on non upgraded vpc router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alena Prokharchyk reopened CLOUDSTACK-5322:
-------------------------------------------
> CreateNetwork command doesnt fails on non upgraded vpc router
> --------------------------------------------------------------
>
> Key: CLOUDSTACK-5322
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5322
> 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
> http://10.147.40.27:8080/client/api?command=createNetwork&response=json&sessionkey=RFrlpoXdvIxKUO5UzITn%2BF6IuYk%3D&zoneId=71c3d210-e0f7-4ea0-80b3-1a3769cdaeb2&vpcid=19dae370-c4db-469d-9328-4966a90f2c09&domainid=1&account=admin&networkOfferingId=700de393-1d94-4f74-94b6-42e1191781f5&name=data-8&displayText=data-8&gateway=10.0.1.1&netmask=255.255.255.0&_=1385966007752
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)