You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "shweta agarwal (JIRA)" <ji...@apache.org> on 2013/06/14 09:10:19 UTC

[jira] [Created] (CLOUDSTACK-3002) Wrong API call when we pass vlan id while configuring VPC network with specify vlan=true network offeringin case of VPC network

shweta agarwal created CLOUDSTACK-3002:
------------------------------------------

             Summary: Wrong API call when we pass vlan id while configuring VPC network with specify vlan=true network offeringin case of VPC network
                 Key: CLOUDSTACK-3002
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3002
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: UI
    Affects Versions: 4.2.0
         Environment: build: CloudStack-non-OSS-MASTER-472-rhel6.3
            Reporter: shweta agarwal
             Fix For: 4.2.0


Repro steps:
1. Create a VPC enabled , vlan= true network offerings
2. Create a VPC network
3. Configure VPC network and select network offering created in step 1 . when we select vlan=true netwok offerings it shows vlan text field .Add entries and click ok

Bug:
Gets error message
Vlan has to be specified; corresponding offering says specifyVlan=true
 API calls is

http://10.147.59.209:8080/client/api?command=createNetwork&response=json&sessionkey=mmuaZLx4FL2vz7RnFMi0WRS085A%3D&zoneId=40a2948d-5070-4d1f-ac7f-10329f30afb8&vpcid=cd2b916c-b249-400e-817e-00ba6575fa34&domainid=fe01fe14-d3ee-11e2-b066-06d2960000b9&account=admin&networkOfferingId=a7be2264-6811-44bb-8466-fdf12fbc5ed5&name=vv&displayText=vv&gateway=10.0.3.1&netmask=255.255.255.0&_=1371193675763

Expectation
When We select a offering with vlan=true , it should fire api with vlanid also


Tried the scenario with API and it passes

attaching required snapshots


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira