Description of problem: The node-tuning ClusterOperator resource does not specify enough related resources. This hinders problem-determination as tools cannot automatically collect the information needed to debug issues. The operator should specify, at minimum, a namespace and a configuration resource to collect. Here is an example from kube-apisever: kind: ClusterOperator metadata: name: kube-apiserver status: relatedObjects: - group: operator.openshift.io name: cluster resource: kubeapiservers - group: '' name: openshift-config resource: namespaces - group: '' name: openshift-config-managed resource: namespaces - group: '' name: openshift-kube-apiserver-operator resource: namespaces - group: '' name: openshift-kube-apiserver resource: namespaces A new e2e test designed to catch this deficiency will white-list this component initially. This component should be removed from the white-list as part of resolving this issue. https://github.com/openshift/origin/blob/master/test/extended/operators/clusteroperators.go (link will be active once https://github.com/openshift/origin/pull/23044 merges)
Upstream PR. https://github.com/openshift/cluster-node-tuning-operator/pull/62
https://github.com/openshift/cluster-node-tuning-operator/pull/64 merged
Verified with NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE node-tuning 4.1.0-0.nightly-2019-06-26-044128 True False False 43m openshift-cluster-node-tuning-operator/ ├── apps │ ├── daemonsets │ │ └── tuned.yaml │ ├── daemonsets.yaml │ ├── deployments.yaml │ ├── replicasets.yaml │ └── statefulsets.yaml ├── apps.openshift.io │ └── deploymentconfigs.yaml ├── autoscaling │ └── horizontalpodautoscalers.yaml ├── batch │ ├── cronjobs.yaml │ └── jobs.yaml ├── build.openshift.io │ ├── buildconfigs.yaml │ └── builds.yaml ├── core │ ├── configmaps │ │ ├── tuned-profiles.yaml │ │ └── tuned-recommend.yaml │ ├── configmaps.yaml │ ├── events.yaml │ ├── pods.yaml │ ├── replicationcontrollers.yaml │ ├── secrets.yaml │ ├── serviceaccounts │ │ └── tuned.yaml │ └── services.yaml ├── image.openshift.io │ └── imagestreams.yaml ├── openshift-cluster-node-tuning-operator.yaml ├── pods │ ├── cluster-node-tuning-operator-5c8848575-nnfmz │ │ ├── cluster-node-tuning-operator │ │ │ └── cluster-node-tuning-operator │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── cluster-node-tuning-operator-5c8848575-nnfmz.yaml │ ├── tuned-h8bf6 │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-h8bf6.yaml │ ├── tuned-kttrm │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-kttrm.yaml │ ├── tuned-n2xkj │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-n2xkj.yaml │ ├── tuned-qz9nc │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-qz9nc.yaml │ ├── tuned-rcktj │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-rcktj.yaml │ └── tuned-smxtv │ ├── tuned │ │ └── tuned │ │ └── logs │ │ ├── current.log │ │ └── previous.log │ └── tuned-smxtv.yaml ├── route.openshift.io │ └── routes.yaml └── tuned.openshift.io └── tuneds └── default.yaml 42 directories, 45 files
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-2019:1635