I know, but I would like to know how I have to fix that, because the bugfix will be deployed with SW 1.8 only. That's not really nice because I am not able to register KVM guests for the next 4 weeks.
From: Paul Robert Marino Sent: Friday, June 15, 2012 1:04 AM To: [email protected] Subject: Re: [Spacewalk-list] Cannot register KVM guest on KVM host #811646 - heads up Yea this is a known bug in 1.7 On Jun 12, 2012 3:53 PM, "Dirk Hartel" <[email protected]> wrote: Here the output of postgresql-Tue.log: ERROR: -20287 : (invalid_entitlement) - The server can not be entitled to the specified level CONTEXT: SQL statement "SELECT rhn_exception.raise_exception ('invalid_entitlement')" PL/pgSQL function "entitle_server" line 49 at PERFORM STATEMENT: SELECT rhn_entitlements.entitle_server(1000010024, E'provisioning_entitled') ERROR: current transaction is aborted, commands ignored until end of transaction block STATEMENT: select ca.label arch, c.id, c.parent_channel, c.org_id, c.label, c.name, c.summary, c.description, to_char(c.last_modified, 'YYYYMMDDHH24MISS') last_modified, rhn_channel.available_chan_subscriptions(c.id, E'1') available_subscriptions from rhnChannel c, rhnChannelArch ca where c.channel_arch_id = ca.id and c.id = rhn_channel.base_channel_for_release_arch( E'6Server', E'x86_64', E'1', 1) On Tuesday 12 June 2012 20:33:17 Dirk Hartel wrote: > Hi, > I have also the same problem. After I reinstalled spacewalk from not > working 1.8 knightly build to 1.7, registering KVM guests is not possible: > > # rhnreg_ks --activationkey=1-a181fc46034b15d18dc3dcbd117162a1 --force -vvv > D: rpcServer: Calling XMLRPC registration.welcome_message > D: opening db environment /var/lib/rpm cdb:mpool:joinenv > D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 > D: locked db index /var/lib/rpm/Packages > D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key > D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key > D: loading keyring from rpmdb > D: opening db index /var/lib/rpm/Name rdonly mode=0x0 > D: added key gpg-pubkey-fd431d51-4ae0493b to keyring > D: added key gpg-pubkey-2fa658e0-45700c69 to keyring > D: added key gpg-pubkey-f21541eb-4a5233e7 to keyring > D: added key gpg-pubkey-897da07a-3c979a7f to keyring > D: added key gpg-pubkey-0608b895-4bd22942 to keyring > D: Using legacy gpg-pubkey(s) from rpmdb > D: opening db index /var/lib/rpm/Providename rdonly mode=0x0 > D: rpcServer: Calling XMLRPC registration.new_system > A protocol error occurred: Internal Server Error , attempt #1, > Error communicating with server. The message was: > Internal Server Error > D: closed db index /var/lib/rpm/Providename > D: closed db index /var/lib/rpm/Name > D: closed db index /var/lib/rpm/Packages > D: closed db environment /var/lib/rpm > > # tail -f rhn_server_xmlrpc.log > 2012/06/12 21:17:33 +02:00 1757 192.168.122.8: > xmlrpc/registration.create_system("token = '1- > a181fc46034b15d18dc3dcbd117162a1'", '6Server', 'x86_64') > 2012/06/12 21:17:34 +02:00 1757 192.168.122.8: > server/rhnVirtualization.guest_registered('ERROR', 'Error adding > entitlement provisioning_entitled: (20287, \'ERROR: -20287 : > (invalid_entitlement) - The server can not be entitled to the specified > level\\nCONTEXT: SQL statement "SELECT rhn_exception.raise_exception > (\\\'invalid_entitlement\\\')"\\nPL/pgSQL function "entitle_server" line 49 > at PERFORM\\n\', InternalError(\'-20287 : (invalid_entitlement) - The > server can not be entitled to the specified level\\nCONTEXT: SQL > statement "SELECT rhn_exception.raise_exception > (\\\'invalid_entitlement\\\')"\\nPL/pgSQL function "entitle_server" line > 49 at PERFORM\\n\',))') > 2012/06/12 21:18:57 +02:00 9556 192.168.122.1: > xmlrpc/up2date.listChannels(1000010001,) > 2012/06/12 22:11:19 +02:00 9648 192.168.122.1: > xmlrpc/up2date.listChannels(1000010001,) > 2012/06/12 22:11:59 +02:00 1753 192.168.122.1: > xmlrpc/registration.welcome_message('lang: None',) > 2012/06/12 22:12:23 +02:00 1756 192.168.122.1: > xmlrpc/registration.update_packages(1000010001, 'packages: 1732') > 2012/06/12 22:16:40 +02:00 1753 192.168.122.8: > xmlrpc/registration.welcome_message('lang: None',) > 2012/06/12 22:17:16 +02:00 9556 192.168.122.1: > xmlrpc/up2date.listChannels(1000010001,) > 2012/06/12 22:17:23 +02:00 1755 192.168.122.8: > xmlrpc/registration.create_system("token = '1- > a181fc46034b15d18dc3dcbd117162a1'", '6Server', 'x86_64') > 2012/06/12 22:17:36 +02:00 1755 192.168.122.8: > server/rhnVirtualization.guest_registered('ERROR', 'Error adding > entitlement provisioning_entitled: (20287, \'ERROR: -20287 : > (invalid_entitlement) - The server can not be entitled to the specified > level\\nCONTEXT: SQL statement "SELECT rhn_exception.raise_exception > (\\\'invalid_entitlement\\\')"\\nPL/pgSQL function "entitle_server" line 49 > at PERFORM\\n\', InternalError(\'-20287 : (invalid_entitlement) - The > server can not be entitled to the specified level\\nCONTEXT: SQL > statement "SELECT rhn_exception.raise_exception > (\\\'invalid_entitlement\\\')"\\nPL/pgSQL function "entitle_server" line > 49 at PERFORM\\n\',))') > 2012/06/12 22:18:31 +02:00 1756 192.168.122.1: > xmlrpc/up2date.listChannels(1000010001,) > 2012/06/12 22:19:03 +02:00 9557 192.168.122.1: > xmlrpc/up2date.login(1000010001,) > ^C > > So the conclusion is, it is like it is; please wait a couple of weeks for > SW 1.8 like mentioned in BZ#811646? > > Cheers > > Dirk > _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list -------------------------------------------------------------------------------- _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
<<Emoticon10.gif>>
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
