Hide Forgot
Description of problem: ================================= Calling run_uri/string with a key containing special characters (dave's $$$) causes the call to time out. This was working in v0.4.4-2. Version-Release number of selected component (if applicable): ================================================================== v0.4.4-4...Also seen running on Fedora with v0.4.5-0.1 How reproducible: ================================= 100% Steps to Reproduce: ================================= sysconfig.run_string('file { "/var/www/html/sysconfig-test":\n owner => root, group => root, mode => 440\n}', 0, 'puppet', "dave's $$$") Actual results: ================================= Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/qmf/console.py", line 308, in <lambda> return lambda *args, **kwargs : self._invoke(name, args, kwargs) File "/usr/lib64/python2.6/site-packages/qmf/console.py", line 452, in _invoke raise RuntimeError("Timed out waiting for method to respond") RuntimeError: Timed out waiting for method to respond
I tried reproducing this with qmf-tool but it didn't happen, can you try? The method call returns an unknown status since it wasn't able to create a file with that name, but it did provide a response instead of timing out. qmf: call 2 run_string 'file { "/tmp/sysconfigtest": owner => root, group => root, mode => 440 }' 0 "puppet" "dave's $$$" Output Parameters: Name Value ================= status unknown
Hrm... I get the same timeout exception when using qmf-tool qmf: call 2 run_string 'file { "/var/www/html/sysconfig-test":\n owner => root, group => root, mode => 440\n}' 0 puppet "dave's $$$" Exception in call command: From Remote Agent: {'error_text': 'Timed out waiting for the agent to respond'}
Fixed upstream: https://github.com/matahari/matahari/commit/48fe329ce099759d7df1bfc2d0a1e54596b3ec7d
This looks good now, marking as verified.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description required.
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. http://rhn.redhat.com/errata/RHBA-2011-1569.html