Bug 1501845

Summary: the router configuration is not reloaded in 10 minutes after adding namespace label
Product: OpenShift Container Platform Reporter: Hongan Li <hongli>
Component: NetworkingAssignee: Ravi Sankar <rpenta>
Networking sub component: router QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs
Version: 3.7.0Keywords: Regression
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Sharded router will notice routes immediately Reason: Otherwise router had to wait up to 2 resync intervals for it to notice which may not be acceptable. Result: Sharded router behavior matches with non-sharded router when routes added or deleted.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:17:21 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 Hongan Li 2017-10-13 10:24:10 UTC 
Description of problem:
If add NAMESPACE_LABELS to router firstly then adding the label to namespace, the router configuration cannot be reloaded in 10 minutes.

Version-Release number of selected component (if applicable):
openshift v3.7.0-0.147.1
kubernetes v1.7.6+a08f5eeb62
etcd 3.2.1


How reproducible:
always

Steps to Reproduce:
1. add NAMESPACE_LABELS to router
   # oc env dc/router NAMESPACE_LABELS=team=red

2. create project, pod, service and route.

3. add label to the project.
   # oc label namespace u1p1 team=red

4. check the router configuration
   # oc rsh router-2-xxxxx cat haproxy.config

Actual results:
Try several times and it need almost 20~30 minutes to load the configuration.

Expected results:
the router configuration should be reloaded in 10 minutes after namespace label changed.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1415112
Comment 1 Ravi Sankar 2017-10-16 22:47:11 UTC 
Fixed in https://github.com/openshift/origin/pull/16039
Comment 2 zhaozhanqi 2017-10-20 06:35:20 UTC 
Verified this bug on v3.7.0-0.158.0

this issue have been fixed. the route will be moved to the correct router once the namespace label changed.
Comment 5 errata-xmlrpc 2017-11-28 22:17:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:3188