Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1441732

Summary:	Router POD does not respiond to new deployments
Product:	OpenShift Container Platform	Reporter:	Vladislav Walek <vwalek>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	router	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	aos-bugs
Version:	3.4.1
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-12 17:29:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vladislav Walek 2017-04-12 15:03:53 UTC

Description of problem:

We are running an OCP 3.4 Cluster in an AWS environment. So far all was running fine, but we now had 2 cases where our customers start deployments in their projects and the appropriate config in the HA proxy router POD did not get changed. So HA-proxy had the old POD IPs in the config and the whole route was not working properly anymore. Routes where the backend POD IP did not change (no new deployment was made) were working fine.

Version-Release number of selected component (if applicable):

Openshift Container Platform: 3.4.1.12-1.git.0.57d7e1d.el7
openshift3/ose-haproxy-router:v3.4.1.12-3

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ben Bennett 2017-04-12 17:29:57 UTC


*** This bug has been marked as a duplicate of bug 1440977 ***