[
https://issues.apache.org/jira/browse/CLOUDSTACK-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918014#comment-13918014
]
Saksham Srivastava commented on CLOUDSTACK-6194:
------------------------------------------------
It is a regression caused due to
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=1f9ad23ba0920700b93cec0ce5f0226ae3c81952;hp=ec191455f4d607e64ca7dfa74cf705ec0f36a083
In case the vlan is passed null to the api, we change it to "untagged"
So in the API in ConfigurationManagerImpl.java
if (vlans != null && vlans.size() > 0) {
VlanVO vlan = vlans.get(0);
if (vlanId == null) {
vlanId = vlan.getVlanTag();
} else if (!NetUtils.isSameIsolationId(vlan.getVlanTag(),
vlanId)) {
throw new InvalidParameterValueException("there is
already one vlan " + vlan.getVlanTag()
The exception is thrown because the vlanId is not null but is "vlan://untagged"
> Failed to increase Shared network IP Range
> ------------------------------------------
>
> Key: CLOUDSTACK-6194
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6194
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server
> Affects Versions: 4.3.0
> Environment: Xenserver, CloudStack 4.3-forward
> Reporter: Saksham Srivastava
> Assignee: Saksham Srivastava
> Fix For: 4.3.0
>
>
> Steps from UI:
> 1. Newly installed setup with Adv zone configuration
> 2. Created shared network
> 3. Tried to Add IP range to the same shared network.
> Observation:
> It failed saying "there is already one vlan 110 on network :212, only one
> vlan is allowed on guest network" .
--
This message was sent by Atlassian JIRA
(v6.2#6252)
