Description of problem: After the hostname for the console's custom route is unset from console operator config, the custom route is still available Version-Release number of selected component (if applicable): 4.5.0-0.ci-2020-04-21-234936 How reproducible: Always Steps to Reproduce: 1. Set the spec of the console operator config with the custom hostname ``` spec: managementState: Managed route: hostname: consolecustom-openshift-console.apps.<cluster-domain> ``` 2. Wait for the custom route to be created 3. Remove the `route` field from the console operator config spec Actual results: The custom route for the console is still available. Expected results: The custom route for the console should be removed. Additional info:
1. Set the spec of the console operator config with the custom hostname ``` spec: managementState: Managed route: hostname: consolecustom-openshift-console.apps.<cluster-domain> ``` 2. Wait for the custom route to be created 3. Remove the `route` field from the console operator config spec The custom console route has been deleted 4.5.0-0.ci-2020-04-22-212726
*** Bug 1826689 has been marked as a duplicate of this bug. ***
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