Description of problem: Customers word from case description : One of our developers created a ticket for openshift origin: https://github.com/openshift/origin/issues/23937 Is there a solution from redhat available for his issue? Version-Release number of selected component (if applicable): OpenShift Master: v3.11.141 Kubernetes Master: v1.11.0+d4cacc0 How reproducible: Always as suggested in above github link. Steps to Reproduce: Refer https://github.com/openshift/origin/issues/23937 Actual results: Refer https://github.com/openshift/origin/issues/23937 Expected results: Refer https://github.com/openshift/origin/issues/23937 Additional info: Will link the case to BZ for more information.
Miciah, would you mind taking this one over? You've done a huge amount of work on it already.
https://github.com/openshift/openshift-controller-manager/pull/53 has been merged for a while now, looks like the bug fell out of sync with GitHub. I fixed it.
Verified with 4.4.0-0.nightly-2020-02-09-220310 and the issue has been fixed. the route is created as below: spec: host: app.test.com path: / port: targetPort: http-default to: kind: Service name: app
Created https://bugzilla.redhat.com/show_bug.cgi?id=1817463 to track a possible 3.11 backport
https://bugzilla.redhat.com/show_bug.cgi?id=1763340 is being used to track a possible 3.11 backport.
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/RHBA-2020:0581