Bug 1368475
| Summary: | python-oslo-rootwrap: Handle renamed executables with KillFilter [OSP6] | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Victor Stinner <vstinner> |
| Component: | python-oslo-rootwrap | Assignee: | Victor Stinner <vstinner> |
| Status: | CLOSED ERRATA | QA Contact: | Asaf Hirshberg <ahirshbe> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 (Kilo) | CC: | aathomas, apevec, dnavale, fdinitto, lhh, nlevinki, srevivo, ushkalim, vstinner |
| Target Milestone: | --- | Keywords: | Reopened, ZStream |
| Target Release: | 6.0 (Juno) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-oslo-rootwrap-1.3.0.0-3.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, after upgrading a service, the oslo.rootwrap was unable to stop the service anymore as the executable was replaced (renamed).
With this update, the renamed executables are handled by using the /proc/$pid/cmdline (if it exists) path, instead of the /proc/$pid/exe path. As a result, the oslo.rootwrap is now able to stop the service properly after an upgrade, even if the executable has been replaced or renamed.
|
Story Points: | --- |
| Clone Of: | 1366697 | Environment: | |
| Last Closed: | 2016-10-05 19:16:20 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: | |||
| Bug Depends On: | 1251211, 1366697, 1368476 | ||
| Bug Blocks: | 1368473 | ||
|
Comment 1
Victor Stinner
2016-08-24 16:11:40 UTC
Automation passed https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS6/job/rhos-jenkins-rhos-6.0-puddle-rhel-7.2-multi-node-packstack-neutron-ml2-gre-rabbitmq-tempest-git-all/37/ the rpm is in the puddle 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://rhn.redhat.com/errata/RHBA-2016-2024.html |