-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.15.0
-
Moderate
-
No
-
False
-
-
* Previously, the Node Tuning Operator (NTO) did not set the `UserAgent` and used a default one. With this update, the NTO sets the `UserAgent` appropriately which makes debugging the cluster easier.
-
Bug Fix
-
In Progress
Description of problem:
As pointed out by https://issues.redhat.com/browse/OCPBUGS-19351 NTO doesn't set the UserAgent and uses a default one. It makes debugging cluster issues harder.
Version-Release number of selected component (if applicable):
All
How reproducible:
Steps to Reproduce:
1. create a TuneD CR which changes kernel command-line parameters, for example: oc create -f- <<EOF apiVersion: tuned.openshift.io/v1 kind: Tuned metadata: name: openshift-bootcmdline-cpu namespace: openshift-cluster-node-tuning-operator spec: profile: - data: | [main] summary=Custom OpenShift profile [bootloader] cmdline=+dummy name: openshift-bootcmdline-cpu recommend: - machineConfigLabels: machineconfiguration.openshift.io/role: "worker" priority: 20 profile: openshift-bootcmdline-cpu EOF
Actual results:
oc get --show-managed-fields mc/50-nto-worker -o yaml | grep manager: manager: Go-http-client
Expected results:
oc get --show-managed-fields mc/50-nto-worker -o yaml | grep manager: manager: cluster-node-tuning-operator
Additional info:
https://issues.redhat.com/browse/OCPBUGS-19351
