Description of problem: Create service with labels, go to route create page as below: https://...project/xiaowan-st/create-route?service=database or https://...project/xiaowan-st/create-route Select a service and click "Copy Service Labels", the link does not work, nothing happened. Version-Release number of selected component (if applicable): OpenShift Master: v3.6.173.0.2 Kubernetes Master: v1.6.1+5115d708d7 How reproducible: Always Steps to Reproduce: 1. oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/sample-app/application-template-stibuild.json 2. Go to Service -> database -> click "Create route", then scroll down to the "Copy Service Labels" and click it 3. Go to Routes page, click "Create Route", then scroll down to the "Copy Service Labels" and click it Actual results: 2&3 Nothing happened. Expected results: 2&3 Since the service is chosen, the labels for database should be filled automatically to route when user click "Copy Service Labels" Additional info:
https://github.com/openshift/origin-web-console/pull/1907
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/6733313b9934f592239260a7ffbe8928f1b5602f Bug 1477933 - Fix copy service labels in create route form Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1477933
Note that the copy service labels link was recently removed (in 3.7). The labels are just prefilled now. https://github.com/openshift/origin-web-console/pull/1940
3.6 backport: https://github.com/openshift/origin-web-console/pull/1964
Verified on OCP OpenShift Master: v3.6.173.0.21 Kubernetes Master: v1.6.1+5115d708d7 Labels could be filled in by "Copy Service Labels": app: ruby-helloworld-sample template: application-template-stibuild The labels from service: labels: app: ruby-helloworld-sample template: application-template-stibuild
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:2642