Description of problem:
Changing the memory manager policy via the kubelet config will drop the node to NotReady state. The reason is that the memory manager assumes that you will delete the memory manager state file during the kubelet restart.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Change the memory manager policy via the KubeletConfig and set the reserved memory.
2. Wait for the node to be ready.
The node stays in the NonReady state forever with the error under the Kubelet logs
Aug 16 18:04:51 alukiano-csbfk-worker-a-dcvzf.c.openshift-gce-devel.internal hyperkube: E0816 18:04:51.711228 9402 memory_manager.go:174] "Could not initialize checkpoint manager, please drain node and remove policy state file" err="could not restore state from checkpoint: [memorymanager] configured policy \"Static\" differs from state checkpoint policy \"None\", please drain this node and delete the memory manager checkpoint file \"/var/lib/kubelet/memory_manager_state\" before restarting Kubelet"
The kubelet should be ready.
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.