Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 12 Jun 2013 10:24:20 +0000 (UTC)
From: "venkata swamybabu budumuru (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12652367.1371032651112.103094.1371032660800@arcas>
In-Reply-To: <JIRA.12652367.1371032651112@arcas>
References: <JIRA.12652367.1371032651112@arcas>
Subject: [jira] [Created] (CLOUDSTACK-2955) [PortableIPrange][UI]
 deletePortableIpRange fails because of UI firing an incorrect API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

venkata swamybabu budumuru created CLOUDSTACK-2955:
------------------------------------------------------

             Summary: [PortableIPrange][UI] deletePortableIpRange fails because of UI firing an incorrect API
                 Key: CLOUDSTACK-2955
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2955
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
         Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4
            Reporter: venkata swamybabu budumuru
            Assignee: Brian Federle


Steps to reproduce :

1. Have latest CS installation with at least 1 advanced zone
2. createPortableIpRange with at least 1 range
3. Try to deletePortableIpRange which was just added in previous step

Observations:

(i) deletePortablIpRange fails with the following error.

Here is the firebug snippet

_	1371032217698
command	deletePortableIpRange
response	json
sessionkey	62Rxynqub3NPvpxcfpUlvhj+1aE=

{ "deleteportablepublicipresponse" : {"uuidList":[],"errorcode":431,"cserrorcode":9999,"errortext":"Unable to execute API command deleteportablepublicip due to missing parameter id"} }

(ii) Above API didn't send the parameter "id" hence it failed in this case.

Attaching all the logs along with db dump to the bug.


--
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