ansible: Try to summarize failure logs #1864
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zmc
force-pushed
the
analyze-ansible
branch
2 times, most recently
from
d246b47
to
312557c
Compare
This provides a more complete interface than what we were constructing. Signed-off-by: Zack Cerza <zack@redhat.com>
The failure logs we capture are sometimes helpful, but are often too long, too complex, and too noisy to understand. Sentry also struggles to associate related failures because of the presence of unique data such as timestamps and URLs. While I don't see a quick and generic solution to this, there are several common failure modes that can easily be summarized. This commit begins that work by looking for errors caused by network outages. Signed-off-by: Zack Cerza <zack@redhat.com>
|
I've scheduled several runs trying to exercise this feature, but I haven't hit the underlying network conditions required. Still, I believe this shows there aren't regressions: https://pulpito-ng.ceph.com/?branch=main&date=2023-07-06 |
dmick
reviewed
Jul 12, 2023
dmick
approved these changes
Jul 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The failure logs we capture are sometimes helpful, but are often too long, too complex, and too noisy to understand. Sentry also struggles to associate related failures because of the presence of unique data such as timestamps and URLs.
While I don't see a quick and generic solution to this, there are several common failure modes that can easily be summarized. This commit begins that work by looking for errors caused by network outages.