[Spacewalk-list] local action status: ((6, ), 'Fatal error in Python code occured', {})

[Dirk Hartel]

Hi Mirek,

here is the events output:
Summary: 	Package Install scheduled by (none)
Details: 	This action will be executed after 07/ 2/12 8:06:24 AM
CEST.

This action's status is: Failed.
The client picked up this action on 07/ 2/12 8:06:44 AM CEST.
The client completed this action on 07/ 2/12 8:06:54 AM CEST.
Client execution returned "Fatal error in Python code occured
[[6]]" (code -1) Packages Scheduled:

    rhn-virtualization-host
    osad

These rpms are part of the activationkey. If Iremove these RPMS from
the activationkey the history shows no errors:

Subscription via Token 	07/2/12 8:15:45 AM CEST 
subscribed to channel rhel-x86_64-tools-6u3 	07/2/12 8:15:43 AM
CEST 
subscribed to channel rhel-x86_64-server-6-3-sub 07/2/12 8:15:43 AM
CEST 
subscribed to channel rhel-x86_64-server-6-3-rs  07/2/12 8:15:43 AM
CEST 
subscribed to channel rhel-x86_64-server-6-3-ha 07/2/12 8:15:43 AM CEST 
subscribed to channel rhel-x86_64-rhn-tools-6u3 07/ 2/12 8:15:43 AM
CEST 
subscribed to channel rhel-x86_64-server-lb-6.3 07/ 2/12 8:15:43 AM
CEST 
subscribed to channel rhel-x86_64-server-epel-6 07/ 2/12 8:15:43 AM CEST
subscribed to channel rhel-x86_64-server-6-3 07/ 2/12 8:15:43 AM CEST 
added system entitlement 07/2/12 8:15:43 AM CEST 
added system entitlement 07/ 2/12 8:15:43 AM CEST 
added system entitlement 07/ 2/12 8:15:43 AM CEST
added system entitlement 07/ 2/12 8:15:43 AM CEST 

but the client still shows the error " action status: ((6,), 'Fatal
error in Python code occured', {})".

rhn_check shows following:

# rhn_check -vv
D: do_call packages.checkNeedUpdate('rhnsd=1',){}
Loaded plugins: refresh-packagekit, rhnplugin
D: login(forceUpdate=False) invoked
:
:
:
'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'} D:
local action status: ((6,), 'Fatal error in Python code occured', {})
D: rpcServer: Calling XMLRPC registration.welcome_message

which is the same for /var/log/up2date

<class 'yum.Errors.RepoError'>: Cannot retrieve repository metadata
(repomd.xml) for repository: rhel-x86_64-rhn-tools-6u3. Pleas e verify
its path and try again

[Mon Jul  2 18:27:52 2012] up2date D: local action status: ((6,),
'Fatal error in Python code occured', {}) [Mon Jul  2 18:27:52 2012]
up2date D: rpcServer: Calling XMLRPC registration.welcome_message


Regards


Dirk

>You see it in events on Spacewalk server?

>In such case it is cause by client code failing so the action was not
>finished properly. If you see system registred in webUI, I would guess
>that the failing script is rhn_check. Try to run it manually on client
>and check output.

>You may also investigate /var/log/up2date.log on client.

>Mirek

>> Hi all, 
>> 
>> I configured a spacewalk proxy 1.7 and I tried to register the first
>> box via the proxy.
>> Every time I got the error 
>> "D: local action status: ((6,), 'Fatal error in Python code occured',
>> {})"
>> The systems looks like registerd (I can see it @ my Spacewalk), but
>> it
>> is not really registered.
>> 
>> Following tools are installed
>> 
>> Client:
>> 
>> rhn-check-1.7.14-1.el6.noarch
>> rhn-client-tools-1.7.14-1.el6.noarch
>> rhncfg-client-5.10.32-1.el6.noarch
>> rhnsd-4.9.15-1.el6.x86_64
>> rhncfg-management-5.10.32-1.el6.noarch
>> yum-rhn-plugin-1.7.2-1.el6.noarch
>> rhncfg-5.10.32-1.el6.noarch
>> rhnlib-2.5.51-1.el6.noarch
>> rhn-setup-1.7.14-1.el6.noarch
>> rhncfg-actions-5.10.32-1.el6.noarch
>> rhnpush-5.5.42-1.el6.noarch
>> rhn-setup-gnome-1.7.14-1.el6.noarch
>> spacewalk-client-repo-1.7-5.el6.noarch
>> spacewalk-backend-libs-1.7.38-1.el6.noarch
>> 
>> Proxy:
>> rhn-setup-1.7.14-1.el6.noarch
>> rhn-client-tools-1.7.14-1.el6.noarch
>> rhncfg-actions-5.10.32-1.el6.noarch
>> rhn-virtualization-host-5.4.14-9.el6sat.noarch
>> rhnlib-2.5.51-1.el6.noarch
>> yum-rhn-plugin-1.7.2-1.el6.noarch
>> rhncfg-client-5.10.32-1.el6.noarch
>> rhnsd-4.9.3-2.el6.x86_64
>> rhncfg-management-5.10.32-1.el6.noarch
>> rhn-setup-gnome-1.7.14-1.el6.noarch
>> rhn-virtualization-common-5.4.14-9.el6sat.noarch
>> rhncfg-5.10.32-1.el6.noarch
>> rhn-org-trusted-ssl-cert-1.0-1.noarch
>> rhnpush-5.5.42-1.el6.noarch
>> rhn-check-1.7.14-1.el6.noarch
>> rhn-org-httpd-ssl-key-pair-fedor-vostro-64-1.0-1.noarch
>> spacewalk-proxy-management-1.7.12-1.el6.noarch
>> spacewalk-certs-tools-1.7.3-1.el6.noarch
>> spacewalk-proxy-redirect-1.7.12-1.el6.noarch
>> spacewalk-proxy-package-manager-1.7.12-1.el6.noarch
>> spacewalk-proxy-broker-1.7.12-1.el6.noarch
>> spacewalk-proxy-installer-1.7.6-1.el6.noarch
>> spacewalk-backend-libs-1.7.38-1.el6.noarch
>> spacewalk-proxy-html-1.1.1-1.el6.noarch
>> spacewalk-backend-1.7.38-1.el6.noarch
>> spacewalk-setup-jabberd-1.6.5-1.el6.noarch
>> spacewalk-proxy-docs-1.1.1-1.el6.noarch
>> spacewalk-repo-1.7-5.el6.noarch
>> spacewalk-proxy-common-1.7.12-1.el6.noarch
>> spacewalk-ssl-cert-check-2.1-1.el6.noarch
>> spacewalk-proxy-selinux-1.1.1-1.el6.noarch



>>-- 

>>Mit freundlichen Grüssen

>>Dirk Hartel

>>Jahnstrasse 3c
>>55263 Wackernheim
>>
>>-- Gesendet von meine Dell Vostro V13