-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Validate systemd unit files #10597
Validate systemd unit files #10597
Conversation
Hi @VannTen. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hum |
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.
@VannTen Thank you for the PR 👍
/ok-to-test
Hi! FYI the CI failure looks related |
Yeah systemd-analyze support for aliasing (actual_filename:unit.name syntax) is only in since v250 (ish) and ubuntu is only on v246 or something like that. |
/ok-to-test |
I added a pretty horrible hack to only check on systemd>= 250 without executing another task. (see the commit message) |
Hmmm I think it could be fine a small fixme comment could be nice to explain that It tries to check systemd version >= 250 and that It should be removed whenever we would no longer support with those systemd versions. Also you should rebase your PR to make the galaxy job happy :D |
This ensure that we fail early if we have a bad systemd unit file (syntax error, using a version not available in the local version, etc)
factory-reset.target was introduced in system 250, same version as the aliasing feature we need for verifying systemd services with ansible. So we only actually executes the validation if that target is present. This is an horrible hack which should be reverted as soon as we drop support for distributions with systemd<250.
9e565f4
to
a4096ae
Compare
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.
Thanks :D!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, MrFreezeex, VannTen The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |
* Validate systemd unit files This ensure that we fail early if we have a bad systemd unit file (syntax error, using a version not available in the local version, etc) * Hack to check systemd version for service files validation factory-reset.target was introduced in system 250, same version as the aliasing feature we need for verifying systemd services with ansible. So we only actually executes the validation if that target is present. This is an horrible hack which should be reverted as soon as we drop support for distributions with systemd<250.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This ensure that we fail early if we have a bad systemd unit file
(syntax error, using a version not available in the local version, etc)
For example it will catch error like the one fixed by #10596
Special notes for your reviewer:
Does this PR introduce a user-facing change?: