For example, from a recent CI run, compare: $ curl -s https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.3/1372/artifacts/e2e-aws/must-gather/registry-svc-ci-openshift-org-ocp-4-3-2019-10-30-020950-sha256-dae1257b516a5c177237cfef5a6a3e241962b0d20cf54bcb2b66dc1671c5035e/cluster-scoped-resources/config.openshift.io/clusteroperators/ingress.yaml | yaml2json | jq -cS '.status.relatedObjects[]' {"group":"","name":"openshift-ingress-operator","resource":"namespaces"} {"group":"operator.openshift.io","name":"","namespace":"openshift-ingress-operator","resource":"IngressController"} {"group":"ingress.operator.openshift.io","name":"","namespace":"openshift-ingress-operator","resource":"DNSRecord"} {"group":"","name":"openshift-ingress","resource":"namespaces"} with: $ curl -s https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.3/1372/artifacts/e2e-aws/must-gather/registry-svc-ci-openshift-org-ocp-4-3-2019-10-30-020950-sha256-dae1257b516a5c177237cfef5a6a3e241962b0d20cf54bcb2b66dc1671c5035e/cluster-scoped-resources/config.openshift.io/clusteroperators/network.yaml | yaml2json | jq -cS '.status.relatedObjects[] | select(.namespace == "cluster-network-operator")' ...no entries... By adding a relatedObjects link to the network ClusterOperator, we can get important things like network-operator logs in the must-gather output.
Verified this bug on 4.3.0-0.nightly-2019-11-11-081655 curl -s https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.3/1372/artifacts/e2e-aws/must-gather/registry-svc-ci-openshift-org-ocp-4-3-2019-10-30-020950-sha256-dae1257b516a5c177237cfef5a6a3e241962b0d20cf54bcb2b66dc1671c5035e/cluster-scoped-resources/config.openshift.io/clusteroperators/network.yaml | grep openshift-network-operator -C 3 relatedObjects: - group: "" name: applied-cluster namespace: openshift-network-operator resource: configmaps - group: apiextensions.k8s.io name: network-attachment-definitions.k8s.cni.cncf.io -- resource: validatingwebhookconfigurations - group: "" name: openshift-service-ca namespace: openshift-network-operator resource: configmaps - group: apps name: multus-admission-controller -- namespace: openshift-sdn resource: daemonsets - group: "" name: openshift-network-operator resource: namespaces versions: - name: operator
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:0062