connectivity: fix panic if the cilium-health test fails #2276
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
Fix a possible panic occurring if the cilium-health test fails and flow validation is enabled, or --print-flow is given. Indeed, that action is configured with a nil destination (as the check has no strict destination target), in turn causing the panic during flow visualization. Hence, let's switch to creating a generic action (i.e., intended for generic assertions), effectively disabling flow collection and display. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
giorio94
force-pushed
the
mio/fix-health-check-panic
branch
from
df0a9e5
to
e313196
Compare
tklauser
approved these changes
Jan 31, 2024
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.
Fix a possible panic occurring if the cilium-health test fails and flow validation is enabled, or --print-flow is given. Indeed, that action is configured with a nil destination (as the check has no strict destination target), in turn causing the panic during flow visualization. Hence, let's switch to creating a generic action (i.e., intended for generic assertions), effectively disabling flow collection and display.
Hit in https://github.com/cilium/cilium-cli/actions/runs/7708934175/job/21020724137?pr=2273