Description of problem: If someone created a route "helloworld.cloudapps.example.com" in one project and another person is trying to create the same route in other project he is able to create it successfully Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. oc project test Now using project "test" on server "https://master.openshift.jas.com:8443". [joe@master ~]$ oc get route NAME HOST/PORT PATH SERVICE LABELS nodejs-route myapp.apps.jas.com nodejs-frontend template=nodejs-example 2. oc project newtest oc edit route eap-app-http-route routes/eap-app-http-route 3. oc get route NAME HOST/PORT PATH SERVICE LABELS eap-app-http-route myapp.apps.jas.com eap-app application=eap-app,template=eap6-basic-sti Actual results: The user is able to create the route successfully and when trying to access both leads to the same page or application. Expected results: The user should be informed and the route should not be created Additional info:
*** This bug has been marked as a duplicate of bug 1214243 ***
A uniqueness check was added so this should no longer be an issue.
Setting status to on QA for testing for OSE. The test cases would be the same as the ones used for: https://bugzilla.redhat.com/show_bug.cgi?id=1214243
varified this bug. when those same route, the later one will refer to the oldest one.
This fix is available in OpenShift Enterprise 3.1.
*** Bug 1302287 has been marked as a duplicate of this bug. ***
*** Bug 1302298 has been marked as a duplicate of this bug. ***
*** Bug 1261843 has been marked as a duplicate of this bug. ***
*** Bug 1306216 has been marked as a duplicate of this bug. ***
*** Bug 1305641 has been marked as a duplicate of this bug. ***
Status write back (telling users what they got) will be in OSE 3.2. The UI and CLI will display information about the hostname the router has on the edge, and the reasons they couldn't get a route created if they didn't. The more general issue of two routes on the same hostname with different ports still needs resolution - we need to ensure it's future compatible with other developments, although we see the value in allowing multiple services to target multiple ports. We can consider allowing a non protected route and protected route to coexist (when passthrough is desired).
We now (in 3.2) will report about the clash. It won't get blocked, but you will be informed.
verified this bug on ]# oc version oc v3.2.0.14 kubernetes v1.2.0-36-g4a3f9c5 when created two same hostname route. the latest one will be 'HostAlreadyClaimed'
*** Bug 1334437 has been marked as a duplicate of this bug. ***
This issue was addressed in OpenShift Enterprise 3.2: https://access.redhat.com/errata/RHSA-2016:1064 As mentioned in its release notes: https://docs.openshift.com/enterprise/3.2/release_notes/ose_3_2_release_notes.html "Routers now report back status to the master about whether routes are accepted, rejected, or conflict with other users. The CLI will now display that error information, allowing users to know that the route is not being served." If there are additional problems with this functionality please create a new bug report.