Bug 1954148 - Console operator is not updating Ingress operator config status with ComponentRoutes conditions.
Summary: Console operator is not updating Ingress operator config status with Componen...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.0
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2021-04-27 16:54 UTC by Jakub Hadvig
Modified: 2023-03-09 01:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-03-09 01:02:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jakub Hadvig 2021-04-27 16:54:54 UTC
Description of problem:
When Ingress operator config is set with a ComponentRoutes for any of the console's routes(console, downloads), console-operator will not update the ingress config with appropriate conditions.

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

How reproducible:

Steps to Reproduce:
1. Upgrade ingress operator config Spec.ComponentRoute with:
- namespace: openshift-console
  name: console
  hostname: console-custom-openshift-console.<cluster-host>
2. Save changes
3. Check ingress operator config Status.ComponentRoutes for appropriate conditions

Actual results:
No conditions are set.

Expected results:
Proper conditions that report the actual state are reported.

Additional info:

Comment 2 Jakub Hadvig 2021-06-11 12:09:15 UTC
Still valid. WIP PR already up -> https://github.com/openshift/console-operator/pull/553

Comment 3 Jakub Hadvig 2021-07-02 16:57:47 UTC
Still valid. PR up and in merge process.

Comment 9 Jakub Hadvig 2022-07-08 13:53:14 UTC
Hey Candance,
I've started to work this issue. Sorry it took a bit longer but we needed to finish work for 4.11.

Comment 10 Shiftzilla 2023-03-09 01:02:33 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.


Note You need to log in before you can comment on or make changes to this bug.