Bug 1926082: Relax the recent log gatherers to avoid degrading during… #332
Conversation
openshift-ci-robot
added
the
bugzilla/severity-high
|
@tremes: This pull request references Bugzilla bug 1926082, 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. |
openshift-ci-robot
added
the
bugzilla/valid-bug
openshift-ci-robot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: psimovec, Sergey1011010, 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 |
|
@tremes: All pull requests linked via external trackers have merged: Bugzilla bug 1926082 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. |
… the upgrade
Gathering pod logs after/during upgrade may fail, because the respective containers may not be ready yet. We shouldn't cause degraded state o the IO in this case.
Categories
Sample archive
No new data added.
Documentation
No doc update
Unit Tests
No new unit test
Privacy
Yes. There are no sensitive data in the newly collected information.
Changelog
References
https://issues.redhat.com/browse/???
https://bugzilla.redhat.com/show_bug.cgi?id=1926082
https://access.redhat.com/solutions/???