You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/10 03:30:09 UTC
[jira] [Commented] (CLOUDSTACK-5425) Egress firewall rules are
broken in the Palo Alto plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843860#comment-13843860 ]
ASF subversion and git services commented on CLOUDSTACK-5425:
-------------------------------------------------------------
Commit 794c17921ba8ca8d57c984c198c2cabee354c9f1 in branch refs/heads/4.3 from [~wstevens]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=794c179 ]
CLOUDSTACK-5425: Fixed egress rules in Palo Alto plugin and removed un-need api commands.
Signed-off-by: Sheng Yang <sh...@citrix.com>
> Egress firewall rules are broken in the Palo Alto plugin
> --------------------------------------------------------
>
> Key: CLOUDSTACK-5425
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5425
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.3.0
> Reporter: Will Stevens
> Assignee: Will Stevens
> Priority: Critical
> Fix For: 4.3.0
>
> Attachments: fixed-egress-rules-master.patch, fixed-egress-rules.patch
>
>
> The introduction of the ability to setup a default egress firewall rule in the network service offering broke the Palo Alto plugin.
> This bug/patch fixes the issues with egress rules in the Palo Alto plugin.
> In addition, I have removed API commands that I had implemented which are not needed...
> eg:
> addExternalFirewall
> deleteExternalFirewall
> listExternalFirewalls
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)