-
Bug
-
Resolution: Done-Errata
-
Major
-
4.12
-
+
-
Moderate
-
No
-
4
-
NHE Sprint 237, NHE Sprint 238, MCO Sprint 240
-
3
-
Rejected
-
False
-
-
-
7/28: moved to mco based on observations from customer debug session
Description of problem:
As a part of Chaos Monkey testing we tried to delete pod machine-config-controller in SNO+1. The pod machine-config-controller restart results in restart of daemonset/sriov-network-config-daemon and linuxptp-daemonpods pods as well.
1m47s Normal Killing pod/machine-config-controller-7f46c5d49b-w4p9s Stopping container machine-config-controller 1m47s Normal Killing pod/machine-config-controller-7f46c5d49b-w4p9s Stopping container oauth-proxy
openshift-sriov-network-operator 23m Normal Killing pod/sriov-network-config-daemon-pv4tr Stopping container sriov-infiniband-cni openshift-sriov-network-operator 23m Normal SuccessfulDelete daemonset/sriov-network-config-daemon Deleted pod: sriov-network-config-daemon-pv4tr
Version-Release number of selected component (if applicable):
4.12
How reproducible:
Steps to Reproduce:
Restart the machine-config-controller pod in openshift-machine-config-operator namespace. 1. oc get pod -n openshift-machine-config-operator 2. oc delete pod/machine-config-controller-xxx -n openshift-machine-config-operator
Actual results:
It restarting the daemonset/sriov-network-config-daemon and linuxptp-daemonpods pods
Expected results:
It should not restart these pod
Additional info:
logs : https://drive.google.com/drive/folders/1XxYen8tzENrcIJdde8sortpyY5ZFZCPW?usp=share_link
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
-
RHEA-2023:5006
rpm
