You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the patch collector, when using the delete operation, we have a poll that ensures that a resource has been deleted. It might fail if a pod is recreated within a second with the same name.
When pods are deleted and re-created with the same name via patch collector, a hook should not return timeout error (false positive)
Actual behavior (what actually happened):
Deleting a pod with non-changing name (owned by a statefulset) should not result in timeout error.
Steps to reproduce:
Apply a delete operation for a statefulset pod which starts quickly enough to rollout in 1 second
Shell operator reports timeout error
Environment:
Deckhouse smoke-mini resheduler hook
Logs
Pod "smoke-mini-d-0" marked for deletion
Module hook failed, requeue task to retry after delay. Failed count is 1. Error: 1 error occurred:
* Delete object v1/Pod/d8-upmeter/smoke-mini-d-0: timed out waiting for the condition
The text was updated successfully, but these errors were encountered:
In the patch collector, when using the delete operation, we have a poll that ensures that a resource has been deleted. It might fail if a pod is recreated within a second with the same name.
shell-operator/pkg/kube/object_patch/patch.go
Line 278 in 6b0058c
Expected behavior (what you expected to happen):
When pods are deleted and re-created with the same name via patch collector, a hook should not return timeout error (false positive)
Actual behavior (what actually happened):
Deleting a pod with non-changing name (owned by a statefulset) should not result in timeout error.
Steps to reproduce:
Environment:
Deckhouse smoke-mini resheduler hook
Logs
The text was updated successfully, but these errors were encountered: