Bug 1723528 - 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.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-24 17:45 UTC by Samuel Padgett
Modified: 2019-10-16 06:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:32:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:32:32 UTC

Description Samuel Padgett 2019-06-24 17:45:35 UTC 
This bug was initially created as a copy of Bug #1722225

I am copying this bug because: 



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-24 17:46:09 UTC 
https://github.com/openshift/console/pull/1745
Comment 3 shahan 2019-06-26 05:04:13 UTC 
It won't show statement that hostname can't be changed after creation when creating route in route form
Verified this bug
4.2.0-0.nightly-2019-06-24-160709
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:24d772dd515d16c28d13de6c349659df0d9807aabb512a25b49d51df82de26d2
Comment 4 errata-xmlrpc 2019-10-16 06:32:20 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:2922
Note You need to log in before you can comment on or make changes to this bug.