test: Enable verbose policy logs to help debug flake #16748
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
The DNSSEC test has been flaky in master, egress connections rejected by lack of an allow policy rule. The client pod is deleted as soon as the connection fails so we can't retrieve policy map contents that way. Instead, we can dump the verbose policy logs and reconstruct an image of the policy map state when the drops happen. Suggested-by: Joe Stringer <joe@cilium.io> Signed-off-by: Paul Chaignon <paul@cilium.io>
pchaigno
added
area/CI
|
test-runtime |
joestringer
approved these changes
Jul 1, 2021
aditighag
approved these changes
Jul 1, 2021
nebril
approved these changes
Jul 2, 2021
pchaigno
added
the
ready-to-merge
|
Runtime test passed and reviews are in. Merging. |
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 DNSSEC test has been flaky in master, egress connections rejected by lack of an allow policy rule. The client pod is deleted as soon as the connection fails so we can't retrieve policy map contents that way. Instead, we can dump the verbose policy logs and reconstruct an image of the policy map state when the drops happen.
Related: #16713.