Hide Forgot
Description of problem: ======================== Trying to do any run_uri or run_string command always results in the daemon crashing. Here is what I tried have tried from qmf and python console: sysconfig.run_uri("http://matahariproject.org/atom.xml", 0, "puppet", "dave") sysconfig.run_uri("http://127.0.0.1/site.pp", 0, "puppet", "dave") sysconfig.run_string('file { "/etc/sudoers":\n owner => root, group => root, mode => 440\n}\n', 0, 'puppet', 'dave') Always results in something like the following in /var/log/messages Aug 11 13:36:41 hp-dl360g5-01 abrt[6299]: saved core dump of pid 6225 (/usr/sbin/matahari-qmf-sysconfigd) to /var/spool/abrt/ccpp-2011-08-11-13:36:41-6225.new/coredump (23089152 bytes) Aug 11 13:36:41 hp-dl360g5-01 abrtd: Directory 'ccpp-2011-08-11-13:36:41-6225' creation detected Aug 11 13:36:41 hp-dl360g5-01 abrtd: Package 'matahari-sysconfig' isn't signed with proper key Aug 11 13:36:41 hp-dl360g5-01 abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2011-08-11-13:36:41-6225 (res:2), deleting Version-Release number of selected component (if applicable): ============================================================== matahari-sysconfig-0.4.2-5.el6.x86_64 with: puppet-server-2.6.6-1.el6_0.noarch puppet-2.6.6-1.el6_0.noarch How reproducible: ================= 100% Steps to Reproduce: ==================== 1. install/start matahari broker and sysconfig agent 2. either through qmf-tool or python console, run the above commands
Awaiting review on ML
I am still seeing this as an issue in v0.4.2-6 with the same version of puppet.
Adam: which patch were/are you waiting review for? Has it been committed? I don't see one referencing this bug number. Please do not put bugs into POST until the patch has been pushed upstream.
https://fedorahosted.org/pipermail/matahari/2011-August/001610.html
https://github.com/matahari/matahari/commit/3c4e275ea7ea977b018cff4fac34ff5ca047bd30
good 2 go in v0.4.2-9
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