ci: emit a namespace report of kube-system on failure #27
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
This can help us capture and debug any intermittent failure that I've seen happen when I use this action in other repo's. For example, a failure to get calico up and running successfully.
consideRatio
force-pushed
the
pr/debug-on-error
branch
from
d5cc136 to
dfc6064
Compare
consideRatio
changed the title
manics
approved these changes
Jan 22, 2021
Yeah it is not ideal, action-k8s-namespace-report preferably shouldn't do that :§ |
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.
I initially considered if we could make it part of the action to debug itself on failure, but it wasn't possible to reference the namespace report action from the action itself. So, instead I'm opting to add a debugging step to our tests of the action.
There is a somewhat seldom occurring intermittent issue where we fail to get up and running, being stuck waiting for calico for example. When this has happened I have had no clear way to debug it, so I figure if it happens within this repo's tests we should at least have some debugging information available.
The kind of failures I've seen are the following, and I hope to find more information about this if it happens in general.