Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3BA7D1086A for ; Wed, 3 Jun 2015 04:55:50 +0000 (UTC) Received: (qmail 42436 invoked by uid 500); 3 Jun 2015 04:55:49 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 42397 invoked by uid 500); 3 Jun 2015 04:55:49 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 42388 invoked by uid 500); 3 Jun 2015 04:55:49 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 42385 invoked by uid 99); 3 Jun 2015 04:55:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jun 2015 04:55:49 +0000 Date: Wed, 3 Jun 2015 04:55:49 +0000 (UTC) From: "Kenneath Park (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-8535) Add LB rule with same ip address to VPC Internal LB problem MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenneath Park updated CLOUDSTACK-8535: -------------------------------------- Description: 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 see 9085 port service in CS UI with same vip. Is there any related issue? Please help me. :( Thanks in advance. was: 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. > 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 see 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)