Bug 1381743
Summary: | In RHEL7, systemd-notify --ready fails, but directly using NOTIFY_SOCKET works (& both work in Fedora24) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Ryan Sawhill <rsawhill> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | bblaskov, fsumsal, jsynacek, rmetrich, rsawhill, systemd-maint-list |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | systemd-219-40.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 09:09:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ryan Sawhill
2016-10-04 21:21:08 UTC
One final data point: if I copy /usr/bin/systemd-notify from F24 (again, systemd-229-15.fc24) to RHEL 7.3 and use that, it works. I can't reproduce this with systemd-219-30.el7. Could you please verify? (In reply to Jan Synacek from comment #2) > I can't reproduce this with systemd-219-30.el7. Could you please verify? Uhh what?? Yes if I follow the exact steps from description I can still reproduce. I just tried: - fresh rhel 7.3 (systemd-219-30.el7) - updated rhel 7.3 (systemd-219-30.el7_3.9) - fresh rhel 7.4beta (systemd-219-39.el7) Everything behaves the same as how I described back on 2016-10-04. `systemd-notify --ready` doesn't work, but writing READY=1 to socket from python works fine. I think that I found the culprit, systemd in upstream adds PPID to every message, ours does not do that. If systemd does not get it, it tries to find the unit from which the message was send, but that is extremely racy. https://github.com/lnykryn/systemd-rhel/pull/124 qa_ack+ for RHEL 7.4 fix merged to upstream staging branch -> https://github.com/lnykryn/systemd-rhel/commit/5a282fc000a52fe98a31ac69832678b1d1d5778d https://github.com/lnykryn/systemd-rhel/commit/6f755a0934a1806a187076f9757064d3e973d1d2 -> post Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2297 |