/var/log/up2date says: [Wed May 5 13:43:17 2010] up2date Traceback (most recent call last): File "/usr/sbin/rhn_check", line 283, in __run_action (status, message, data) = CheckCli.__do_call(method, params) File "/usr/sbin/rhn_check", line 275, in __do_call method = getMethod.getMethod(method, "/usr/share/rhn/", "actions") File "/usr/share/rhn/up2date_client/getMethod.py", line 78, in getMethod actions = __import__(modulename) File "/usr/share/rhn/actions/packages.py", line 266, in <module> yum_base = YumAction() File "/usr/share/rhn/actions/packages.py", line 62, in __init__ self.doConfigSetup(debuglevel=rhncli.cfg["debug"]) <type 'exceptions.AttributeError'>: 'module' object has no attribute 'cfg' I *think* this results in: Client execution returned "Fatal error in Python code occured [[6]]" (code -1) in the WebUI for all events (i.e. anything that runs through rhn_check) even if the task is successful (i.e. rhn_check -vvv does). The traceback might be unrelated to this tho. Version: rhn-check-1.0.0-1.fc12.noarch Additional Information: <roysjosh> red_alert, jsherrill, seems like this commit is responsible for your traceback: 2fa678d4153e2a072d8c1953c3c5a16b7a1d080c <roysjosh> it removes cfg from up2date_client/rhncli.py
Actually, it's 8d915a17b46d5e83a1b06d60b51c0e7ed36bf714 which seems to be out of line.
Additional tests show that this definitely happens in different cases: - applying updates - deploying config files Also, if rhn_check is called with -vvv the following is always logged just after the traceback: [Wed May 5 14:57:59 2010] up2date D: local action status: ((6,), 'Fatal error in Python code occured', {}) So I guess those two things are really only one problem.
went ahead and added the cfg back into rhncli.py master: a437034484fb40034f59c209bb95f0c912776519 spacewalk 1.0 backport: bfa90ae335a79f88390d20894eed52bb0900c4b4
*** Bug 587888 has been marked as a duplicate of this bug. ***
Packages built: yum-rhn-plugin-1.0.2-1 rhn-client-tools-1.0.6-1
Changed the fix a little: da27aded48e9710465a55a72d845d23779005a8d
This is definitely fixed in 1.0 and nightly, thanks.
(In reply to comment #8) > This is definitely fixed in 1.0 and nightly, thanks. Aligning to space10 and closing.