WIP [release-4.9] Bug 2047416: restart pod on non-retriable failures when deleting stale objects#936
Conversation
|
@flavio-fernandes: This pull request references Bugzilla bug 2047416, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: flavio-fernandes The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
In cases where we currently miss doing retries for removal of stale objects, it is best to restart the pod than simply log an error and bring the pod up. This change is changing that behavior on functions run early on the pod start up. Conflicts: go-controller/pkg/ovn/pods.go go-controller/pkg/ovn/policy.go Signed-off-by: Flavio Fernandes <flaviof@redhat.com> (cherry picked from commit 7954229)
513fdf3 to
db006dd
Compare
|
@flavio-fernandes: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/hold |
|
This change has been folded into #981 . |
In cases where we currently miss doing retries for removal of stale
objects, it is best to restart the pod than simply log an error and
bring the pod up. This change is changing that behavior on functions
run early on the pod start up.
Conflicts:
go-controller/pkg/ovn/pods.go
go-controller/pkg/ovn/policy.go
Signed-off-by: Flavio Fernandes flaviof@redhat.com
(cherry picked from commit 033cc76)