You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Murali Reddy (JIRA)" <ji...@apache.org> on 2013/07/05 13:31:48 UTC

[jira] [Updated] (CLOUDSTACK-234) create/delete firewa/lb/pf rule: send ip assoc command only on first rule is created on the IP and last rule is revoked on the IP

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Murali Reddy updated CLOUDSTACK-234:
------------------------------------

    Summary: create/delete firewa/lb/pf rule: send ip assoc command only on first rule is created on the IP and last rule is revoked on the IP  (was: create/delete firewa/lb/pf rule: send ip assoc command just for the IP for which you are creating the rule)
    
> create/delete firewa/lb/pf rule: send ip assoc command only on first rule is created on the IP and last rule is revoked on the IP
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-234
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-234
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.0.0
>            Reporter: Alena Prokharchyk
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
>
>
> We have to improve the logic for creating/deleting any kind of firewall rules. At the moment ipAssoc is being called when:
> * the first rule for the ip address is being created
> * the last rule for the IP address is being removed
> As a part of ipAssoc command, we send all ip addresses assigned to the guest network of the rule. The behavior has to be fixed the way we send ip assoc only for the ip address the rule is being created for.

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