Bug 1477933
Summary: | Copy Service Labels on route creating page does not work | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> |
Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
Status: | CLOSED ERRATA | QA Contact: | XiaochuanWang <xiaocwan> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.0 | CC: | aos-bugs, jokerman, mmccomas, yapei |
Target Milestone: | --- | ||
Target Release: | 3.6.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the "Copy Service Labels" link in the "Create Route" form did not correctly copy the labels from the service to the new route. It has been fixed to copy the selected service's labels.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-08 03:15:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
XiaochuanWang
2017-08-03 09:24:32 UTC
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 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 |