Bug 1722225
| Summary: | Create route form incorrectly states that hostnames can't be changed | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Samuel Padgett <spadgett> |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, sponnaga, wsun, yanpzhan |
| Target Milestone: | --- | ||
| Target Release: | 4.1.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | 4.1.6 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the web console create route form incorrectly stated that route hostnames cannot be changed after creation. This is not always the case and depends on the specific user's permissions. The incorrect help text has been removed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-07-23 18:12:07 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
Samuel Padgett
2019-06-19 18:03:04 UTC
4.1.0-0.nightly-2019-07-03-205519 console image：quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5c27c8002781fbee929e3a3aeceb20ae1be0a227ab8f121ff86d125ae8094d83 Checked on OCP 4.1 env with above version. Now on route create form , it shows "Public hostname for the route. If not specified, a hostname is generated.", there is no message "The hostname cannot be changed after the route is created." The bug has been fixed, so move it to Verified. 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-2019:1766 |