Bug 1168010

Summary: PuppetSSH fails on RHEL 7
Product: Red Hat Satellite Reporter: Mike Burns <mburns>
Component: Foreman ProxyAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: UnspecifiedCC: achan, bbuckingham, cwelton, dcleal, jmontleo, mburns
Target Milestone: UnspecifiedKeywords: 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
Description of problem:
Upstream Issue:  http://projects.theforeman.org/issues/7859

Boils down to bad escaping on ruby 1.9+

https://github.com/theforeman/smart-proxy/commit/ccd77aaecf66be4ad57fe43d06b0c9cb3f313f93

Version-Release number of selected component (if applicable):
foreman-proxy-1.6.0.30-1.el6sat

How reproducible:
always

Comment 2 Dominic Cleal 2014-11-26 08:45:05 UTC
foreman-proxy-1.6.0.30-1.el6sat runs on Ruby 1.8, why is this an issue?

Comment 4 Mike Burns 2014-11-26 13:09:28 UTC
(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

Comment 7 Corey Welton 2014-12-11 14:40:14 UTC
Can we get some additional information/steps to reproduce?

Comment 8 Mike Burns 2014-12-11 16:57:08 UTC
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.

Comment 9 Mike McCune 2014-12-11 17:24:33 UTC
temp move to MOD for ET

Comment 11 Bryan Kearney 2015-01-09 14:50:11 UTC
Upstream bug assigned to lzap

Comment 12 Lukas Zapletal 2015-01-15 16:30:51 UTC
I VERIFIED it on the system.

Comment 15 errata-xmlrpc 2015-01-16 21:08:03 UTC
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