Closed Lennonka closed 2 months ago
The PR preview for 4bbc64a3fe1f8bc5add3b6b5615b1be553ebbfab is available at theforeman-foreman-documentation-preview-pr-3303.surge.sh
The following output files are affected by this PR:
@evgeni Technical ack, please? Is the verification sufficient as mentioned in the description?
The diff matches what we discussed, yes.
I'd prefer if someone could actually setup an external DHCP using this procedure and verify it works, because I did not.
I've requested QE testing on my team.
Hello,
tsig-keygen
works. Tested configuring the external DHCP server with it, I didn't see any issues with RHEL8/9
@asteflova Can you please give me a formal ack on the style so that I can merge it?
After careful consideration, I've decided not to make further changes regarding the key name. I don't think we have to document every option. Providing just the key name that works out of the box seems sufficient.
Cherry-picked:
What changes are you introducing?
Replacing
dnssec-keygen
withtsig-keygen
. TheHMAC-MD5
algorithm is not supported bydnssec-keygen
on EL 9, but the algorithm is required for Foreman.The
tsig-keygen
command also works on EL 8.Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Because of EL 9 support. The
tsig-keygen
command should be preferred on EL 8 as well.https://issues.redhat.com/browse/SAT-27986
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
I have tested that the
tsig-keygen
command is available on both RHEL 9 and 8, and gives the required output.Unlike
dnssec-keygen
, which generates files,tsig-keygen
only outputs text on the console and doesn't create any files. Therefore, no files have to be deleted afterwards.Checklists
Please cherry-pick my commits into: