Bug 1302298

Summary: editing the hostname of the route to the existing one in another project is not properly handled
Product: OKD Reporter: Jeremy Choi <jechoi>
Component: RoutingAssignee: Maru Newby <mnewby>
Status: CLOSED DUPLICATE QA Contact: zhaozhanqi <zzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, eparis, ramr
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-02-01 14:48:45 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 Jeremy Choi 2016-01-27 12:41:09 UTC
Description of problem:

When a developer edits her route, if new hostname entered is the same as the one which already exists in another project, the route will seem to be  successfully updated when doing 'oc get route', but the old hostname will still serves the requests to the service. Additionally, in this case, even if the developer deletes the route, the old hostname will still do the same.

Version-Release number of selected component (if applicable):
oc v1.1.1.1
kubernetes v1.1.0-origin-1107-g4c8e6f4

How reproducible:
100%

Steps to Reproduce:
1. create a project and an app and expose it with 'www.example.com' as a hostname 
2. create another project and an app and expose it with 'www2.example.com' 
3. edit the hostname of the route in (2) from 'www2.example.com' to 'www.example.com'
4. send request to 'www2.example.com'
5. delete the route in (2)
6. send request to 'www2.example.com'

Actual results:
When doing 'oc get route' after (3), the route has been modified to 'www.example.com', but the requests were able to be made to the service via 'www2.example.com'.

Expected results:
A proper error handling is required.

Additional info:

Comment 1 Ram Ranganathan 2016-01-27 19:20:21 UTC
The actual issue is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1243664 
even if the "route" to get to the same issue is different.

Comment 2 Jeremy Choi 2016-01-28 00:54:19 UTC
Thanks for the pointer of the previous bug. The deletion case also needs to be examined.

Comment 3 Eric Paris 2016-02-01 14:48:45 UTC

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