-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
3
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem
Currently the autoscaler requests MachineAutoscalers and ClusterAutoscaler and a namespace get collected via ClusterOperator's relatedObjects. But the autoscaler is using that information to drive MachineSet's, and it would make debugging easier if those MachineSets were also collected, e.g. in oc adm inspect clusteroperator/cluster-autoscaler.
Version-Release number of selected component
At least 4.19. Likely old, but maybe not worth backporting. In must-gathers, some other component will mention it wants MachineSets, so this is really just about cleaning up oc adm inspect clusteroperator/cluster-autoscaler.
How reproducible
Every time.
Steps to Reproduce
$ oc get -o json clusteroperator cluster-autoscaler | jq -c '.status.relatedObjects[]'
Actual results
{"group":"autoscaling.openshift.io","name":"","namespace":"openshift-machine-api","resource":"machineautoscalers"} {"group":"autoscaling.openshift.io","name":"","namespace":"openshift-machine-api","resource":"clusterautoscalers"} {"group":"","name":"openshift-machine-api","resource":"namespaces"}
Expected results
Also mention Machine-API (and Cluster-API?) MachineSets.