Bug 1722225 - Create route form incorrectly states that hostnames can't be changed
Summary: Create route form incorrectly states that hostnames can't be changed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.1.z
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard: 4.1.6
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-19 18:03 UTC by Samuel Padgett
Modified: 2019-07-23 18:12 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-07-23 18:12:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1766 0 None None None 2019-07-23 18:12:15 UTC

Description Samuel Padgett 2019-06-19 18:03:04 UTC 
The console create route form says that a hostname can't be changed after creation. This is wrong. It can be changed depending on a user's RBAC permission. We should remove the incorrect statement.
Comment 1 Samuel Padgett 2019-06-19 18:03:54 UTC 
https://github.com/openshift/console/pull/1752
Comment 3 Yanping Zhang 2019-07-04 08:15:21 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.
Comment 5 errata-xmlrpc 2019-07-23 18:12:07 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.