[
https://issues.apache.org/jira/browse/CLOUDSTACK-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-2651:
----------------------------------
Component/s: (was: Network Controller)
UI
Description:
Steps:
1. Have an CS setup with advanced zone/ Advanced zone with SG.
2. Create a shared network(zone->physical network->Guest->Add guest network).
3. Try to entend the ip range for the created guest network.(zone->physical
network->Guest-> <created guest network> ->view ip ranges->add ip range)
Observation:The API passed for extending the ip range is
API
passed:http://10.147.38.154:8080/client/api?command=createVlanIpRange&forVirtualNetwork=false&networkid=2bc91f46-8f4a-4a31-b95d-ecea71663e67&startip=10.147.54.238&endip=10.147.54.239&response=json&sessionkey=ax2q1vd%2Bp4BsOPgw%2BKQ78JKMVx0%3D&_=1369311736447";
Response is
{ "createvlaniprangeresponse" :
{"errorcode":431,"cserrorcode":4350,"errortext":"Gateway, netmask and zoneId
have to be passed in for virtual and direct untagged networks"} }
Expected behaviour:
Extending ip range for the already existing network should ask for parameters
like gateway and netmask otherwise user can't add guest ip range in different
subnet.
Attached the screen shot for reference.
was:
Steps:
1. Have an CS setup with advanced zone.
2. Create a shared network(zone->physical network->Guest->Add guest network).
3. Try to entend the ip range for the created guest network.(zone->physical
network->Guest-> <created guest network> ->view ip ranges->add ip range)
Observation:The API passed for extending the ip range is
API
passed:http://10.147.38.154:8080/client/api?command=createVlanIpRange&forVirtualNetwork=false&networkid=2bc91f46-8f4a-4a31-b95d-ecea71663e67&startip=10.147.54.238&endip=10.147.54.239&response=json&sessionkey=ax2q1vd%2Bp4BsOPgw%2BKQ78JKMVx0%3D&_=1369311736447";
Response is
{ "createvlaniprangeresponse" :
{"errorcode":431,"cserrorcode":4350,"errortext":"Gateway, netmask and zoneId
have to be passed in for virtual and direct untagged networks"} }
Expected behaviour:
Extending ip range for the already existing network should not ask for
parameters like gateway,netmask and zoneid.
Attached the screen shot for reference.
Summary: [Shared n/w]Add IP range should ask for gateway and netmask
(was: [Shared n/w]Extending the guest network IP range should not mandate the
parameters netmask,gateway and zoneid)
> [Shared n/w]Add IP range should ask for gateway and netmask
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-2651
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2651
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Affects Versions: 4.2.0
> Reporter: manasaveloori
> Assignee: Bharat Kumar
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: guestnetwork.jpg
>
>
> Steps:
> 1. Have an CS setup with advanced zone/ Advanced zone with SG.
> 2. Create a shared network(zone->physical network->Guest->Add guest network).
> 3. Try to entend the ip range for the created guest network.(zone->physical
> network->Guest-> <created guest network> ->view ip ranges->add ip range)
> Observation:The API passed for extending the ip range is
> API
> passed:http://10.147.38.154:8080/client/api?command=createVlanIpRange&forVirtualNetwork=false&networkid=2bc91f46-8f4a-4a31-b95d-ecea71663e67&startip=10.147.54.238&endip=10.147.54.239&response=json&sessionkey=ax2q1vd%2Bp4BsOPgw%2BKQ78JKMVx0%3D&_=1369311736447";
> Response is
> { "createvlaniprangeresponse" :
> {"errorcode":431,"cserrorcode":4350,"errortext":"Gateway, netmask and zoneId
> have to be passed in for virtual and direct untagged networks"} }
> Expected behaviour:
> Extending ip range for the already existing network should ask for
> parameters like gateway and netmask otherwise user can't add guest ip range
> in different subnet.
> Attached the screen shot for reference.
--
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
