cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Kumar (JIRA)" <>
Subject [jira] [Comment Edited] (CLOUDSTACK-2651) [Shared n/w]Add IP range should ask for gateway and netmask
Date Thu, 30 May 2013 09:39:20 GMT


Bharat Kumar edited comment on CLOUDSTACK-2651 at 5/30/13 9:39 AM:

the public ips belong to the pod, they do not belong to the network. 
      was (Author: bharat.kumar):
    Also reading from the network part is already being done to check if it  a range is being
added to same subnet or a different one. 
> [Shared n/w]Add IP range should ask for gateway and netmask
> -----------------------------------------------------------
>                 Key: CLOUDSTACK-2651
>                 URL:
>             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:"
> 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:

View raw message