Bug 1168010
| Summary: | PuppetSSH fails on RHEL 7 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Mike Burns <mburns> |
| Component: | Foreman Proxy | Assignee: | Lukas Zapletal <lzap> |
| Status: | CLOSED ERRATA | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | Unspecified | CC: | achan, bbuckingham, cwelton, dcleal, jmontleo, mburns |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/7859 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
On a Red Hat Enterprise Linux 7 system, ruby upgrades changed the accepted format for io.popen resulting in ssh puppet commands being incorrectly formatted. This prevented the commands from executing. The format has been corrected in this fix.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-01-16 21:08:03 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
Mike Burns
2014-11-25 21:02:19 UTC
foreman-proxy-1.6.0.30-1.el6sat runs on Ruby 1.8, why is this an issue? (In reply to Dominic Cleal from comment #2) > foreman-proxy-1.6.0.30-1.el6sat runs on Ruby 1.8, why is this an issue? Sorry, it's .el7sat Can we get some additional information/steps to reproduce? I'm not sure how this gets done through Satellite in general, but a host running RHEL 7 when triggering puppetssh to run on the host will fail with errors similar to the issue linked in the summary. We've tested and validated this works in our OpenStack setup. temp move to MOD for ET Upstream bug assigned to lzap I VERIFIED it on the system. 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-2015:0054 |