incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1241) Network apply rules logic is broken
Date Tue, 12 Feb 2013 09:57:12 GMT


ASF subversion and git services commented on CLOUDSTACK-1241:

Commit 513f8b98e9b7818d0b37c9641d9021b77a0cfc45 in branch refs/heads/4.1 from [~murali.reddy]
[;h=513f8b9 ]

CLOUDSTACK-1241: Network apply rules logic is broken

added logic to check if the network element is configured service
provider for the network before applying rules

> Network apply rules logic is broken
> -----------------------------------
>                 Key: CLOUDSTACK-1241
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.1.0
> ApplyRules logic in both LoadBalancingRulesManager and FirewallManager loops through
all the network elements corresponding to a service. There is no check to ensure that network
element is supposed to be provider of the service in that network. Not all network elements
are not returning False, in case they fail to apply rule (applyFWRules, applyPFRules, applyStaticNats,
applyNetworkACLs, applyLBRules) as they can not handle the rule. This results in applyrules
logic to succeed even though rules are not applied on any provider.

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