Bug 2055415
Summary: | Possible race condition in console operator managed cluster sync | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jon Jackson <jonjacks> |
Component: | Management Console | Assignee: | Jon Jackson <jonjacks> |
Status: | CLOSED WONTFIX | QA Contact: | Yadan Pei <yapei> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.11 | CC: | aos-bugs, kcormier |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-22 18:28:24 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
Jon Jackson
2022-02-16 21:14:09 UTC
Jon I have a feeling that we are not picking up the configmap informer's event that the managed-clusters.yaml CM was updated. I see that we are filtering based on the label https://github.com/openshift/console-operator/blob/master/pkg/console/operator/operator.go#L152 wondering if that's not causing race. I encountered a problem today where a managed cluster was not added to the cluster switcher. @jonjacks believes it was an instance of this issue, and he was able to resolve the problem by forcing deployment of new console pods. Migrated to Jira: https://issues.redhat.com/browse/OCPBUGS-4008 |