[PR #5914/3da24d50 backport][stable-5] dig lookup: fix DNSKEY's algorithm handling #5915
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.
This is a backport of PR #5914 as merged into main (3da24d5).
SUMMARY
With dnspython 2.0.0+,
algorithm
of DNSKEY rdata is an enum type and no longer an int. Explicitly converting it toint
makes sure that it is an integer.Try
ansible localhost -m debug -a 'msg={{ q("dig", "com", qtype="DNSKEY", flat=0) }}'
with and without this PR, then you getvs
(I also updated the RRSIG field name list, while being at it.)
ISSUE TYPE
COMPONENT NAME
dig lookup plugin