cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Livens (JIRA)" <j...@apache.org>
Subject [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
Date Wed, 23 Mar 2016 13:19:25 GMT

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

Mime
View raw message