Bug 1415218
| Summary: | sshd sometimes does not correctly write pid file | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Gabriele Cerami <gcerami> |
| Component: | openssh | Assignee: | Jakub Jelen <jjelen> |
| Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.3 | CC: | gcerami, jjelen, jpichon, michele, pmyers, royoung, salmy, sclewis, systemd-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-23 14:57:01 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
Gabriele Cerami
2017-01-20 15:18:00 UTC
This is known problem. SSHD writes it always correctly, but systemd is unable to track it (tries to read it in wrong moments, does not re-read it and is unnecessarily noisy). We have already filled two related bugs #1381997 and #1398360. Unfortunately, there is no known solution except "building against systemd" as Debian does now (which is not acceptable by upstream [1]). But we certainly want to address this in RHEL7.4 so patience, unless it has very high priority to get it fixed earlier. [1] https://bugzilla.mindrot.org/show_bug.cgi?id=2641 Thanks for the quick info Jakub, much appreciated ;) Since we started seeing this only recently with version 6.6.1p1-31-el7 and we did not see it previously with 6.6.1p1-25-el7, if we somehow would manage to revert to that version would that be an okay workaround or were we just lucky and the -25 version is affected as well? Thanks, Michele Or any other workarounds as it seems it is not entirely trivial to pin openssh to a previous version in our CI infrastructure. Thanks The previous version had a problem with related issue (bug #1291172) which got fixed, but this awkward behavior showed up (and slipped though our testing). You revert the commit below (change in service file) to restore the old behavior: --- a/sshd.service +++ b/sshd.service @@ -5,8 +5,10 @@ After=network.target sshd-keygen.service Wants=sshd-keygen.service [Service] +Type=forking +PIDFile=/var/run/sshd.pid EnvironmentFile=/etc/sysconfig/sshd -ExecStart=/usr/sbin/sshd -D $OPTIONS +ExecStart=/usr/sbin/sshd $OPTIONS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure @jjelen: This bug affects some percentage (10%) of all RHOSP users trying to install RHOSP undercloud on top of RHEL 7.3 Unfortunately, the workaround proposed above which might help us in our CI environments, is not suitable really to bake into our RHOSP Director images. I have set the prio/sev to this to High because it results in an install failure which will affect customers and our field users. The only reason it is not urgent is because it's not 100% reproducible and only affects folks in an intermittent fashion. Can we please investigate a resolution to this issue and prioritize the fix for a backport to 7.3.z once the fix is uncovered? @salmy Please see comment 17 above on the context and urgency on this. @michele, @gcerami can provide risk assessment of adding to z-stream. Closing this bug. Please lets continue discussion in the duplicate. I will update the other bug with the proposed solution so also the other customers can verify the proposed solution. *** This bug has been marked as a duplicate of bug 1381997 *** |