You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Brian Federle (JIRA)" <ji...@apache.org> on 2013/07/11 00:29:49 UTC
[jira] [Resolved] (CLOUDSTACK-2983) [UI]Creation of ACL rule with
protocol number immediately after ICMP rule is failing.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Federle resolved CLOUDSTACK-2983.
---------------------------------------
Resolution: Fixed
> [UI]Creation of ACL rule with protocol number immediately after ICMP rule is failing.
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2983
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2983
> 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: Brian Federle
> Fix For: 4.2.0
>
>
> Steps:
> 1. Have a CS with advanced zone.
> 2. Create a VPC.
> 3. Create an ACL list.
> 4. Under that ACL list create ICMP rule(Ingress/Egress)
> 5. Now select protocol as “protocol number” and try to create a rule.
> Observations:
> 1. Both ICMP and protocol number does not allow user to enter “Rule number”
> 2. After successful creation of ICMP rule if we select protocol as “protocol number” wrong API is getting passed with icmpcode and icmptype.
> http://10.147.38.154:8080/client/api?command=createNetworkACL&response=json&sessionkey=LFtfMql5WYk5TiZDpK66h7PiuNk%3D&cidrlist=10.0.0.0%2F0&action=Allow&protocol=16&icmptype=-1&icmpcode=-1&traffictype=Egress&aclid=dca04bf0-6997-4890-a880-9590e5e3f796&_=1371117947027
--
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