Bug #2662
closed
Failed puppet run: undefined method `escape_for_shell' for Proxy::Puppet:Module
Added by Ivan Necas over 11 years ago.
Updated over 6 years ago.
Description
$subject$ when trying to puppetrun via smart-proxy.
Changing:
def self.escape_for_shell(command)
to
def escape_for_shell(command)
Seems to work. I wonder, if there is a context where the original code works as well?
- Priority changed from Normal to Urgent
- Target version set to 1.2.0
I'm running my custom build based on aff8fa8b4f7108b30c3e2ff6ec9068c9851e4d91, it seems the recent git doesn't have the problem, but I agree that escape_for_shell was there for a reason, so it should get back.
Thanks for REALLY quick response :)
Ivan - do you have a backtrace for this? Looks like Proxy::Util.escape_for_shell is not being used anywhere in smart-proxy/devel...
Dmitri Dolguikh wrote:
Ivan - do you have a backtrace for this? Looks like Proxy::Util.escape_for_shell is not being used anywhere in smart-proxy/devel...
See the above comments, I accidentally removed the code in the second SHA above. This issue now becomes: please restore 216728d09495fe5a2940760df702910642853bca but without the undefined method bug :)
- Status changed from New to Assigned
- Assignee set to Anonymous
- Status changed from Assigned to Ready For Testing
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Target version deleted (
1.2.0)
Also available in: Atom
PDF