Bug 1725006
| Summary: | The 4.1 Cluster Console does not allow the creation of Routes with multiple service endpoints, which was one of the features of the 3.x dev UI | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ian Lawson <ian.lawson> |
| Component: | Management Console | Assignee: | Joe Caiani <jcaiani> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aos-bugs, jcaiani, jokerman, mmccomas, spadgett, yanpzhan |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Because of the changes between 3.x and 4.x there were some features that were not in sync.
Consequence: The 4.1 Cluster Console does not allow the creation of Routes with multiple service endpoints in the UI, which was one of the features of the 3.x dev UI. In 4.x this feature is available by editing the yaml of a route, however, it is missing in the GUI Route form.
Fix: Add the ability in the GUI form to add/remove up to 3 alternate service endpoints.
Result: The configuration of multiple service endpoints on a route is now in sync with the 3.11 version of openshift via both yaml and forms.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-23 11:04:15 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
Ian Lawson
2019-06-28 09:00:47 UTC
4.3.0-0.nightly-2019-10-20-140322 Checked on OCP 4.3 with above payload version, now creating route with multiple services from form is available on console. The bug is fixed. 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:0062 |