-
Notifications
You must be signed in to change notification settings - Fork 384
edns: allow dnsconfd name resolution for kickstart fetching #6353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
edns: allow dnsconfd name resolution for kickstart fetching #6353
Conversation
Start dnsconfd already before kickstart fetching. We used to start dnsconfd only after the kickstart was fetched if kickstart usage was detected so that the potential certificates from kikcstart are applied. But this mechanism ruled out use case when dnsconfd (name resolution) is needed for the kickstart fetching. So start the dnsconfd early and if certificates were fetched restart it (it is done by restarting unbound service as recommended by dnsconfd). Resolves: RHEL-83931
We need this guard because kickstart may be fetched over multiple network devices and it is parsed after each fetching. Parsing itself should be idempotent (multiple parsing harmless) as it only dumps files with configuration / options for further actions. Resolves: RHEL-83931
|
/kickstart-test --testtype dns |
|
/kickstart-test --testtype smoke |
|
/build-image |
|
Images built based on commit 49b058b:
Download the images from the bottom of the job status page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @rvykydal - I've reviewed your changes - here's some feedback:
Overall Comments:
- It looks like the
start_dnsconfdfunction now takes a stage and a reason, but some call sites only pass a reason - can you ensure all call sites are updated to pass both arguments? - Consider adding a comment to explain why
PYTHONHASHSEEDis being set.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
jkonecny12
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Port of upstream #6258
Resolves: RHEL-83931