Hide Forgot
Description of problem: Should update the KCM resource-graph timely with the latest configure Version-Release number of selected component (if applicable): payload: 4.7.0-0.nightly-2021-01-19-095812 How reproducible: always Steps to Reproduce: 1) Check the KCM resource-graph with command : `oc exec po/kube-controller-manager-operator-86ccb6fb8c-xrc4s -- cluster-kube-controller-manager-operator resource-graph |dot -Tpng >output0121.png` Actual results: 1) From the result picture show the comfigmap serviceaccount-ca in openshift-kube-controller-manager is unioned from comfigmap initial-serviceaccount-ca in openshift-config and configmap default-ingress-cert in openshift-config-managed . But actruly can’t find the configmap initial-serviceaccount-ca in project openshift-config. Expected results: 1) update the KCM resource-graph timely with the latest configure. Additional info:
Created attachment 1749368 [details] Resource Graph
This is internal utility, so I'm lowering the priority.
initial-serviceaccount-ca CM in openshift-config NS is hardcoded in the code [1] and marked as static. [1] https://github.com/openshift/cluster-kube-controller-manager-operator/blob/master/pkg/cmd/resourcegraph/resourcegraph.go#L115
The same is here: https://github.com/openshift/cluster-kube-apiserver-operator/pull/217/commits/9b202cc15292080155559ef6921621482ad2bc9a#diff-94947abf30c57f88e9c7cd7193e20d019c71e27b00b639dc5aac07654f409bd3R55
Need more time to understand what the graph is supposed to do and how to improve the logic.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
still could be reproduced.
The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
took me a long time to tackle this, posted a PR with updated resources (there is a lot of new resources)
Checked with latest version , the issue has fixed : oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-04-23-153426 True False 135m Cluster version is 4.11.0-0.nightly-2022-04-23-153426 steps: 1) extract the resource-graph from kcm-operator pods: oc exec po/kube-controller-manager-operator-55d887cf7b-qmgpt -- cluster-kube-controller-manager-operator resource-graph |dot -Tpng >output0424.png 2) check the comfigmap serviceaccount-ca in openshift-kube-controller-manager is unioned from comfigmap kube-apiserver-server-ca in openshift-config-managed and configmap default-ingress-cert in openshift-config-managed
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069