mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-22 19:31:44 +00:00
Make sure kubelet is restarted in the storage test
In some storage tests, kubelet is stopped first and the test check node NotReady state. However, if it fails to have this state, kubelet could not be restarted because the defer function is placed after the stop kubelet command. This PR fixes this issue.
This commit is contained in:
parent
bc79dcfd05
commit
9de354034b
@ -220,13 +220,13 @@ func TestVolumeUnmountsFromDeletedPodWithForceOption(c clientset.Interface, f *f
|
||||
Expect(result.Code).To(BeZero(), fmt.Sprintf("Expected grep exit code of 0, got %d", result.Code))
|
||||
}
|
||||
|
||||
// This command is to make sure kubelet is started after test finishes no matter it fails or not.
|
||||
defer func() {
|
||||
KubeletCommand(KStart, c, clientPod)
|
||||
}()
|
||||
By("Stopping the kubelet.")
|
||||
KubeletCommand(KStop, c, clientPod)
|
||||
defer func() {
|
||||
if err != nil {
|
||||
KubeletCommand(KStart, c, clientPod)
|
||||
}
|
||||
}()
|
||||
|
||||
By(fmt.Sprintf("Deleting Pod %q", clientPod.Name))
|
||||
if forceDelete {
|
||||
err = c.CoreV1().Pods(clientPod.Namespace).Delete(clientPod.Name, metav1.NewDeleteOptions(0))
|
||||
|
Loading…
Reference in New Issue
Block a user