Red Hat Bugzilla – Bug 1421990
option '--wildcard-policy=' cannot work for 'oc expose svc'
Last modified: 2017-07-24 10:11 EDT
Description of problem: Using 'oc expose svc' to create wildcard route with option '--wildcard-policy=Subdomain'. the column 'WILDCARD' of route still be 'None' Version-Release number of selected component (if applicable): # openshift version openshift v3.5.0.20+87266c6 kubernetes v1.5.2+43a9be4 etcd 3.1.0 How reproducible: always Steps to Reproduce: 1. Create service oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/routing/unsecure/service_unsecure.json -n z1 2. Create wildcard route oc expose service service-unsecure --hostname=wildcard.0214-0ml.qe.rhcloud.com --wildcard-policy=Subdomain -n z1 3. check the route oc get route Actual results: step 3 # oc get route service-unsecure -n z1 NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD service-unsecure wildcard.0214-0ml.qe.rhcloud.com service-unsecure http None Expected results: the route should be wildcard route when using 'Subdomin' Additional info:
Origin PR: https://github.com/openshift/origin/pull/12954
Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/94c654d58336de796df0bba6ab50c8a078b86b11 change the parameter names in the route generation function to match the oc expose flag name When the wildcardpolicy flag was changed to wildcard-policy the GeneraterParam was left unchanged this mismatch caused the wildcard-policy to be ignored and always appear as none when using oc expose Bug 1421990
This has been merged into ocp and is in OCP v3.5.0.21 or newer.
Verified this bug on OCP v3.5.0.21
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-2017:0884