-
Notifications
You must be signed in to change notification settings - Fork 2.9k
test/system: quadlet use correct systemd restart policy #18758
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
Conversation
Systemd doesn't support `never` and logs a warning, systemd uses no as default so we do not have to specify it at all. Check systemd.service(5) for the systemd docs. Fixes containers#18743 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99 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 |
|
@edsantiago PTAL |
|
if @edsantiago is hip with this, LGTM |
|
LGTM but I think it's more than just that one test: $ ack 'Restart.*nev'
cmd/podman/common/create.go
634: [removed, I think this one is OK, it's not systemd]
contrib/systemd/system/podman-play-kube@.service
10:Restart=never
pkg/util/utils.go
674: if strings.ToLower(splitRestart[0]) == "never" {
[I think this one is ok also]And, in the process of searching for combinations of restart+never (while ignoring the kube restartPolicy), I found: podman/test/system/250-systemd.bats Lines 450 to 462 in 5543de2
which seems to be obsolete. Would you be willing to take those on as part of this PR? If not, np, I can file an issue. I'm just not comfortable submitting a PR because there are edge cases I'm sure I haven't considered. |
This is not checked into git, I do not have such file locally. Looks like it was renamed and then fixed in d7f6d35 The 250-systemd test change I cannot really tell we should wait for @vrothberg to comment on that. It tests the behavior without exit policy and the kube template does not set one so it is fine IMO. |
|
Ack, thanks. And sorry for false-alarming on a dead file. /lgtm |
|
Opened #18854 to remove the confusing comment. |
Systemd doesn't support
neverand logs a warning, systemd uses no as default so we do not have to specify it at all.Check systemd.service(5) for the systemd docs.
Fixes #18743
Does this PR introduce a user-facing change?