[
https://issues.apache.org/jira/browse/CLOUDSTACK-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
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
ConfigurationManagerImpl.java when it checks vlanId for null since we wiped out
Vlan.UNTAGGED.
> [Automation] createVlanIpRange API failing, if you pass VLAN
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-5502
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5502
> 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 filed
> 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)
> http://xxx.xxxx.xxx.xxx:8096/?command=createVlanIpRange&gateway=10.223.251.1&forvirtualnetwork=false&startip=10.223.251.3&podid=0253bcbf-e636-4776-9e8c-216b70d195a2&zoneid=a9912aa8-a231-44d9-a70b-9d53e6db2d27&netmask=255.255.255.192&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
(v6.1.5#6160)
