Bug 1829236

Summary: Missing e2e tests for customURL feature in console-operator
Product: OpenShift Container Platform Reporter: Jakub Hadvig <jhadvig>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, jokerman, yapei
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: missing e2e tests for the console's customURL feature in the console-operator. Consequence: Additional changes to the customURL logic could lead to regressions. Fix: Add e2e test for the customURL. Result: CI will test setting and unsetting of the customURL to prevent regressions when merging changes into the console-operator repo.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:32:50 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 Jakub Hadvig 2020-04-29 09:22:32 UTC
Description of problem:
We are missing e2e tests for the console's customURL feature in the console-operator. Need to provide them in order to prevent feature regression.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Yadan Pei 2020-05-09 05:50:32 UTC
I think this bug can be verified since PR was already merged https://github.com/openshift/console-operator/blob/master/test/e2e/custom_url_test.go

Comment 4 errata-xmlrpc 2020-07-13 17:32:50 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-2020:2409