-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Install systemd-resolved on CentOS 8 and 9 #246
Merged
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
On CentOS 8 and 9 systemd-resolved must be installed to use systemd-resolved. Install the package if `manage_resolved` is `true`. Since the `systemd_internal_services` fact will only be populated once the package is installed a second puppet run will be required to actually configure systemd-resolved.
kenyon
approved these changes
Feb 11, 2022
I cross-checked with a CentOS 8 Stream system, and the same seems to apply there (no separate |
traylenator
added a commit
to traylenator/puppet-systemd
that referenced
this pull request
Feb 21, 2022
MR voxpupuli#246 started installing the `systemd-resolved` package on RedHat 8 and 9 however this quite wrong for 8 where systemd-resolved is not a sub package. ``` > rpm -qf /usr/bin/systemd-resolve systemd-239-56.el8.x86_64 ```
traylenator
added a commit
to traylenator/puppet-systemd
that referenced
this pull request
Feb 21, 2022
Following voxpupuli#246 and voxpupuli#254 systemd-resolved was installed on family RedHat 9 only. On RedHat 7 a systemd-resolved package is now installed. For information it is only RedHat 8 that does not have a systemd resolved package.
traylenator
added a commit
to traylenator/puppet-systemd
that referenced
this pull request
Feb 21, 2022
Following voxpupuli#246 and voxpupuli#254 systemd-resolved was installed on OS family RedHat 9 only. On RedHat 7 a systemd-resolved package is now installed as it is available. For information it is only RedHat 8 that does not have a systemd-resolved package.
traylenator
added a commit
to traylenator/puppet-systemd
that referenced
this pull request
Feb 21, 2022
Following voxpupuli#246 and voxpupuli#254 systemd-resolved was installed on OS family RedHat 9 only. On RedHat 7 a systemd-resolved package is now installed as it is available. For information it is only RedHat 8 that does not have a systemd-resolved package.
traylenator
added a commit
to traylenator/puppet-systemd
that referenced
this pull request
Feb 21, 2022
Following voxpupuli#246 and voxpupuli#254 systemd-resolved was installed on OS family RedHat 9 only. On RedHat 7 a systemd-resolved package is now installed as it is available. For information it is only RedHat 8 that does not have a systemd-resolved package.
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.
Pull Request (PR) description
On CentOS 8 and 9 systemd-resolved must be installed to use
systemd-resolved.
Install the package if
manage_resolved
istrue
which is not the default.Since the
systemd_internal_services
fact will only be populatedonce the package is installed a second puppet run will be required
to actually configure systemd-resolved.