-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.14.z
-
Critical
-
None
-
OCPNODE Sprint 257 (Green)
-
1
-
False
-
-
-
Description of problem:
After performing several reboots, SNO fails to come back into a running state. It can sometimes be recovered with additional reboots (may require more than one to recover). However, in at least one instance the node never recovered after 10+ reboots. kubelet and crio services start appropriately, however, pods fail to deploy and the following error is observed: rpc error: code = Unknown desc = failed to pin namespaces [0xc000177b90 0xc000177bc0 0xc000177bf0]: taskset: failed to set pid 10248's affinity: Invalid argument
Version-Release number of selected component (if applicable):
How reproducible:
Not easily reproducible. Issue may occur after any given reboot. Node tuning may also be a factor in reproducing
Steps to Reproduce:
1. Reboot SNO 2. 3.
Actual results:
etcd and other critical pods fail to deploy siting a namespace pinning / affinity error
Expected results:
All pods deploy and enter a running state
Additional info:
- is related to
-
OCPBUGS-32407 Systemd processes not being moved to cpuset/systemd.slice
- Closed