cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <>
Subject [jira] [Reopened] (CLOUDSTACK-5502) [Automation] createVlanIpRange API failing, if you pass VLAN
Date Thu, 26 Dec 2013 19:56:51 GMT


Marcus Sorensen reopened CLOUDSTACK-5502:

Can we fix this in a different way? 'untagged' should be a completely valid option (e.g. I
deploy a zone with a bridge that is public, and I want to use that bridge as-is). It breaks
my test suites, and maybe the way a lot of individuals are used to deploying advanced zones,
instead of being lenient it now throws "Vlan id is required when add ip range to the public
network" in when it checks vlanId for null since we wiped out

> [Automation] createVlanIpRange API failing, if you pass VLAN 
> -------------------------------------------------------------
>                 Key: CLOUDSTACK-5502
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.3.0
>         Environment: KVM Basic Zone with SG
>            Reporter: Rayees Namathponnan
>            Assignee: Daan Hoogland
>            Priority: Blocker
>             Fix For: 4.3.0
> This issue found in KVM basic zone with SG automation run;  test cases from below suite
> integration.component.test_multiple_ip_ranges.
> Steps to reproduce 
> Step 1 :  Create basic zone with SG
> Step 2 : Crete IP VLAN Range with below command (pass vlan=untagged)
> Result;
> API command failed with error 
> { "createvlaniprangeresponse" : {"uuidList":[],"errorcode":431,"cserrorcode":4350,"errortext":"Vlan
doesn't match vlan of the network"} }
> this API command works only, if you are not passing any VLAN

This message was sent by Atlassian JIRA

View raw message