Verified on 4.2.0-0.ci-2019-06-24-155129 oc adm must-gather collects the resources and pod logs related to node tuning. 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-55cb59fd78-df6pf │ │ ├── cluster-node-tuning-operator │ │ │ └── cluster-node-tuning-operator │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── cluster-node-tuning-operator-55cb59fd78-df6pf.yaml │ ├── tuned-4gc48 │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-4gc48.yaml │ ├── tuned-64t5t │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-64t5t.yaml │ ├── tuned-czhqf │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-czhqf.yaml │ ├── tuned-f4bgv │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-f4bgv.yaml │ ├── tuned-mzgtn │ │ ├── tuned │ │ │ └── tuned │ │ │ └── logs │ │ │ ├── current.log │ │ │ └── previous.log │ │ └── tuned-mzgtn.yaml │ └── tuned-p9kkl │ ├── tuned │ │ └── tuned │ │ └── logs │ │ ├── current.log │ │ └── previous.log │ └── tuned-p9kkl.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:2922