Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "kubelet: use static CPU manager policy by default" #1465

Merged
merged 1 commit into from
Apr 8, 2021

Conversation

gthao313
Copy link
Member

@gthao313 gthao313 commented Apr 7, 2021

This reverts commit 227640c.

Description of changes:
Revert this change since it triggers failed to start kubelet during migration.

error

Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal kubelet[3496]: I0407 19:44:44.416175    3496 state_mem.go:36] [cpumanager] initializing new in-memory state store
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal kubelet[3496]: E0407 19:44:44.417137    3496 container_manager_linux.go:329] failed to initialize cpu manager: could not initialize checkpoint manager: could not restore state from checkpoint: configured policy "static" differs from state checkpoint policy "none"
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal kubelet[3496]: Please drain this node and delete the CPU manager checkpoint file "/var/lib/kubelet/cpu_manager_state" before restarting Kubelet.
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal kubelet[3496]: F0407 19:44:44.417153    3496 server.go:273] failed to run Kubelet: could not initialize checkpoint manager: could not restore state from checkpoint: configured policy "static" differs from state checkpoint policy "none"
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal kubelet[3496]: Please drain this node and delete the CPU manager checkpoint file "/var/lib/kubelet/cpu_manager_state" before restarting Kubelet.
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal systemd[1]: kubelet.service: Failed with result 'exit-code'.
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal systemd[1]: Failed to start Kubelet.
Apr 07 19:44:44 ip-192-168-85-94.us-west-2.compute.internal systemd[1]: Reached target Multi-User System.

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

@gthao313 gthao313 merged commit 368afb1 into bottlerocket-os:develop Apr 8, 2021
@tjkirch tjkirch added this to the 1.0.8 milestone Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants