Bug 1764227

Summary:	Incorrect validation pattern on ConsoleCLIDownloads Href field
Product:	OpenShift Container Platform	Reporter:	Samuel Padgett <spadgett>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, jhadvig, jokerman, spadgett, xiaocwan, yapei
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1764224	Environment:
Last Closed:	2019-11-13 18:56:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1764224
Bug Blocks:

Description Samuel Padgett 2019-10-22 13:46:40 UTC

+++ This bug was initially created as a clone of Bug #1764224 +++

Description of problem:
Validation pattern on ConsoleCLIDownloads Href field is to restrictive.

Version-Release number of selected component (if applicable):
4.3.0-0.ci-2019-10-21-030544

How reproducible:
Always

Steps to Reproduce:
1. Go to `/k8s/cluster/console.openshift.io~v1~ConsoleCLIDownload/~new`
2. Add trailing slash to the `href` field
3. 

Actual results:
Error will ocurre:
Error "Invalid value: "": spec.links.href in body should match '^https://([\w-]+.)+[\w-]+(/[\w- ./?%&=])?$'" for field "spec.links.href".

Expected results:
CR will be created

Additional info:

Comment 2 XiaochuanWang 2019-10-28 07:21:50 UTC

Check with 'https://www.example.com/' and it does successfully saved, the actual download link on page after created will remove the trailing slash.
This could be Verified.
Tested on 4.2.0-0.nightly-2019-10-27-140004

Comment 4 errata-xmlrpc 2019-11-13 18:56: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:3303