-
Bug
-
Resolution: Done
-
Critical
-
4.13.z, 4.12.z, 4.14, 4.15
-
Critical
-
No
-
CNF Compute Sprint 239, CNF Compute Sprint 240, CNF Compute Sprint 241, CNF Compute Sprint 242, CNF Compute Sprint 243, CNF Compute Sprint 244, CNF Compute Sprint 245
-
7
-
Rejected
-
False
-
-
-
Description of problem:
Pods are being terminated on Kubelet restart if they consume any device. In case of CNV this Pods are carrying VMs and the assuption is that Kubelet will not terminate the Pod in this case.
Version-Release number of selected component (if applicable):
4.14 / 4.13.z / 4.12.z
How reproducible:
This should be reproducable with any device plugin as far as goes my understanding
Steps to Reproduce:
1. Create Pod requesting device plugin 2. Restart Kubelet 3.
Actual results:
Admission error -> Pod terminates
Expected results:
No error -> Existing & Running Pods will continue running after Kubelet restart
Additional info:
The culprit seems to be https://github.com/kubernetes/kubernetes/pull/116376
- is cloned by
-
OCPBUGS-19479 CNV regression with recent Kubernetes rebase - device plugin
- Closed
- relates to
-
OCPNODE-1687 Impact assessment of OCPBUGS-14605
- Closed
- links to
-
RHEA-2023:7198 rpm
(1 links to)