You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nick Livens (JIRA)" <ji...@apache.org> on 2016/03/23 14:19:25 UTC
[jira] [Assigned] (CLOUDSTACK-9321) Multiple Internal LB rules
(more than one Internal LB rule with same source IP address) are not
getting resolved in the corresponding InternalLbVm instance's haproxy.cfg
file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Livens reassigned CLOUDSTACK-9321:
---------------------------------------
Assignee: Nick Livens
> Multiple Internal LB rules (more than one Internal LB rule with same source IP address) are not getting resolved in the corresponding InternalLbVm instance's haproxy.cfg file
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9321
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9321
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server, Network Controller
> Reporter: Mani Prashanth Varma Manthena
> Assignee: Nick Livens
> Priority: Critical
> Fix For: 4.9.0
>
>
> Multiple Internal LB rules (more than one Internal LB rule with same source IP address) are not getting resolved in the corresponding InternalLbVm instance's haproxy.cfg file.
> Moreover, each time a new Internal LB rule is added to the corresponding InternalLbVm instance, it replaces the existing one.
> Thus, traffic corresponding to these un-resolved (old) Internal LB rules are getting dropped by the InternalLbVm instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)