Kenneath Park created CLOUDSTACK-8535:
-----------------------------------------
Summary: Add LB rule with same ip address to VPC Internal LB
problem
Key: CLOUDSTACK-8535
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8535
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Virtual Router
Affects Versions: 4.4.0
Reporter: Kenneath Park
In VPC,,
1.Create tier (internal LB function)
2.assign VMs
3.Create Internal LB rule LB1(TCP 9082)
4.Create Internal LB rule LB2 (TCP 9085) with same source ipaddress
(10.11.242.119)
In management log..
2015-06-03 12:59:11,846 DEBUG [o.a.c.n.l.ApplicationLoadBalancerManagerImpl]
(http-8080-exec-149:ctx-d5134530 ctx-1ba95738) IP address 10.11.242.119 is
already used by existing LB rule, returning it
2015-06-03 12:59:11,850 DEBUG [c.c.n.e.F5ExternalLoadBalancerElement]
(http-8080-exec-149:ctx-d5134530 ctx-1ba95738) Scheme Internal is not supported
by the provider F5BigIP
2015-06-03 12:59:11,850 DEBUG [c.c.n.e.OvsElement]
(http-8080-exec-149:ctx-d5134530 ctx-1ba95738) Checking if OvsElement can
handle service Lb on network app-tier
.
.
.
succeeded.
.
BUT, In VR(internal LB)
real port is 9082 only. (haproxy.cfg)
9085 is not seeing and cannot serviced
BUT, I can 9085 port service in CS UI with same vip.
Is there any related issue?
Please help me. :(
Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
