-
Notifications
You must be signed in to change notification settings - Fork 5.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
systemd.py available() breaks on latest LSB-compliant versions of systemd #36671
Comments
New systemd behaviour:
Old behaviour:
|
@wrigtim thanks for the PR! we will get this closed once your PR has been reviewed and merged. |
@wrigtim What version of systemd were you running when you generated that output? According to the git history for systemd, the different output when the unit cannot be found is new in systemd 231, as is the retcode of 4. For instance, this is the result on CentOS 7 running systemd 219:
As far as I can see, the change to the return code to make it properly LSB-compliant when the service is unknown (which is what we're looking for in the |
Replied on PR, but this is 7.3 beta (looks like RedHat have back-ported the upstream changes)... |
Sure - will test Monday in office (don't have 7.3 here). Apologies for the delay but I've been travelling... |
No problem! I'm almost 100% certain that this will work fine, but I don't have 7.3 available to test either, so getting confirmation from you will be a good sanity check. Thanks in advance, and thanks for helping bring this to our attention. |
@terminalmage Looks good to me - thanks very much!
|
@wrigtim Thanks for taking the time to confirm, I really appreciate it! I'll mark this as closed. |
Description of Issue/Question
Later versions of systemctl now follow LSB standards for return codes (https://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/iniscrptact.html). As part of this change the STDOUT was removed and replaced with a simple STDERR response.
Setup
Any host running systemd 219-30 onward (RHEL 7.3, latest Fedora, etc)
Steps to Reproduce Issue
Versions Report
The text was updated successfully, but these errors were encountered: