Details
-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.14
-
None
-
Moderate
-
No
-
Rejected
-
False
-
Description
Description of problem:
Using klog.V(5).Info( instead klog.V(5).Infof(
I0628 15:16:16.218304 2107651 ovspinning_linux.go:145] Managing ovs-vswitchd[%s] daemon CPU affinity1289 I0628 15:16:16.218751 2107651 ovspinning_linux.go:181] Process[%d] CPU affinity already match current process's affinity %s12890-7
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-06-27-000502
How reproducible:
always
Steps to Reproduce:
1. echo 1 > /etc/openvswitch/enable_dynamic_cpu_affinity 2. 3.
Actual results:
I0628 15:16:16.218304 2107651 ovspinning_linux.go:145] Managing ovs-vswitchd[%s] daemon CPU affinity1289 I0628 15:16:16.218751 2107651 ovspinning_linux.go:181] Process[%d] CPU affinity already match current process's affinity %s12890-7
Expected results:
I0628 15:16:16.218304 2107651 ovspinning_linux.go:145] Managing ovs-vswitchd[1289] daemon CPU affinity I0628 15:16:16.218751 2107651 ovspinning_linux.go:181] Process[1289] CPU affinity already match current process's affinity 0-7
Additional info:
Check usage of klog.V(5).Info(
145: klog.V(5).Info("Managing ovs-vswitchd[%s] daemon CPU affinity", ovsVSwitchdPID) 181: klog.V(5).Info("Process[%d] CPU affinity already match current process's affinity %s", targetPID, printCPUSet(currentProcessCPUs))
Attachments
Issue Links
- links to
-
RHSA-2023:5006
OpenShift Container Platform 4.14.z security update