+++ This bug was initially created as a clone of Bug #1691190 +++ Description of problem: Passthrough routes does not support path based routing. Why this route can be created? It should throw an error. But actual result is Route gets created and that is unusable. Replicte 1st scenario: Create a pass-through route with --path variable and it gets created without an error. 2nd Scenario: Create a simple pass-through route. Create one more pass-through route with same hostname as above and give a path to the route. It also gets created. Actual results: it is processed same as other routes. Expected results: In both cases, It should throw an error, While creating pass-through route it should not check for hostname+path combination, and should throw an error stating not supported.
https://github.com/openshift/origin/pull/25578 Tagging with UpcomingSprint while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved.
Fix is posted but blocked on CI issues. We'll try to get this done in the upcoming sprint.
Fix is posted but still blocked on CI issues (although some of the earlier issues have been resolved). We'll continue working on getting this through CI in the upcoming sprint.
Still investigating CI issues. We'll try to get this through in the upcoming sprint.
Still blocked on CI issues.
Still blocked on CI issues (recent failures look like docker.io rate limiting).
Need to follow up with PM as to how we will handle this and other 3.11 BZs that have been languishing in CI.
verified with v3.11.501 and passed [root@ip-172-18-15-133 ~]# oc version oc v3.11.501 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-172-18-15-133.ec2.internal:8443 openshift v3.11.501 kubernetes v1.11.0+d4cacc0 create passthrough route firstly, then try to create http, edge and reencrypt route with same host and a path, only http can work, others are showed as "HostAlreadyClaimed". [root@ip-172-18-15-133 ~]# oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD myedge HostAlreadyClaimed /test/ service-unsecure http edge None mypath example-hongli.apps.0819-fza.qe.rhcloud.com service-secure https passthrough None myreen HostAlreadyClaimed /test/ service-secure https reencrypt None service-unsecure example-hongli.apps.0819-fza.qe.rhcloud.com /test/ service-unsecure http None create edge route firstly, then create passthrough route with same host: [root@ip-172-18-15-133 ~]# oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD edge2 www.example.com /test/ service-unsecure http edge None pass2 HostAlreadyClaimed service-secure https passthrough None create reen route firstly, then create passthrough route with same host: [root@ip-172-18-15-133 ~]# oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD pass3 HostAlreadyClaimed service-secure https passthrough None reen3 my.test.com /test/ service-secure https reencrypt None
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 (Moderate: OpenShift Container Platform 3.11.z security and bug fix update), 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-2021:3193