New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1919778: Monitors how many gatherings failed in a row, and applies degraded status accordingly #320
Conversation
@0sewa0: This pull request references Bugzilla bug 1919778, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In 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. |
I tested this locally. When there is an error in an imporant gatherer then the retry logic is correctly applied (gathering is running again after some sime and IO is set as degraded for this time period). When there's no gathering error then everything runs as before. We can mark more gatherers as |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 0sewa0, tremes The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@0sewa0: All pull requests linked via external trackers have merged: Bugzilla bug 1919778 has been moved to the MODIFIED state. In 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. |
Tries to solve the issue described in https://bugzilla.redhat.com/show_bug.cgi?id=1919778
Categories
Sample archive
Documentation
Unit Tests
Privacy
Yes. There are no sensitive data in the newly collected information.
Changelog
not necessary
References
https://bugzilla.redhat.com/show_bug.cgi?id=1919778