Bug 1321289

Summary: The route info on some routers will not be reported back to client after route gets updated
Product: OpenShift Container Platform Reporter: Meng Bo <bmeng>
Component: NetworkingAssignee: Solly Ross <sross>
Networking sub component: router QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, sross, tdawson
Version: 3.2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-12 16:34:24 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:

Description Meng Bo 2016-03-25 08:58:29 UTC
Description of problem:
Create two routers with host-network which will serve for the routes in all the namespaces on a multi-tenant env, create route and update the route with user. Check the route info from client side. 

Not all the routers show the updated route.


Version-Release number of selected component (if applicable):
openshift v3.2.0.7
kubernetes v1.2.0-36-g4a3f9c5
haproxy router ef080f3084e8

How reproducible:
always

Steps to Reproduce:
1. Setup multi-node env
2. Create two routers with host-network
# oadm router --replicas=1 --service-account=router router1 --host-network=true
# oadm router --replicas=1 --service-account=router router2 --host-network=true
3. Create a route by any user
# oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/routing/unsecure/list_for_unsecure.json
4. Check the route info via client
5. Update the route
eg, update www.example.com to www1.example.com
6. Check the route info via client again


Actual results:
4.
$ oc describe route
Name:                   route
Created:                25 seconds ago
Labels:                 <none>
Annotations:            <none>
Requested Host:         www.example.com
                          exposed on router router1 29 seconds ago
                          exposed on router router2 30 seconds ago
Path:                   <none>
TLS Termination:        <none>
Insecure Policy:        <none>
Service:                hello-nginx
Endpoint Port:          <all endpoint ports>
Endpoints:              10.129.0.2:80, 10.130.0.2:80


6.
$ oc describe route
Name:                   route
Created:                About a minute ago
Labels:                 <none>
Annotations:            <none>
Requested Host:         www1.example.com
                          exposed on router router1 about a minute ago
                        www.example.com exposed on router router2 about a minute ago
Path:                   <none>
TLS Termination:        <none>
Insecure Policy:        <none>
Service:                hello-nginx
Endpoint Port:          <all endpoint ports>
Endpoints:              10.129.0.2:80, 10.130.0.2:80


Expected results:
The route info on all the routers should be reported back to client side.


Additional info:
Check the haproxy configs on the router pod which does not report back. Can find the route had been updated.
Try to visit the new route via both routers, and both work.

Comment 1 Solly Ross 2016-03-28 20:31:59 UTC
This looks like it may be a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1317835.  I will try to reproduce.

Comment 2 Meng Bo 2016-03-29 07:07:43 UTC
@Solly

This should not be a dup of bz#1317835.
This can be reproduced on latest ose build v3.2.0.8 which above bug had been fixed.

Comment 3 Solly Ross 2016-03-29 14:48:04 UTC
I've reproduced as well.  I'll look into it.

Comment 4 Solly Ross 2016-03-31 13:50:46 UTC
I've submitted a PR against Origin that's currently undergoing review: https://github.com/openshift/origin/pull/8309

Comment 5 Solly Ross 2016-04-01 14:09:28 UTC
The PR above merged.

Comment 6 Troy Dawson 2016-04-04 16:15:38 UTC
Should be in atomic-openshift-3.2.0.11-1.git.0.6696e29.el7, which is now built and in images.

Comment 7 Meng Bo 2016-04-05 06:00:40 UTC
Checked on build 3.2.0.11.

Issue has been fixed.

Comment 9 errata-xmlrpc 2016-05-12 16:34:24 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-2016:1064