According to the GUI there's no universal default key. However, any key I attach to the kickstart profile to set a specific base channel is rejected with the error below unless it matches the architecture of one specific channel. i.e. if I kickstart with RHEL 5 x86_64 autoreg works fine without any additional key. However, kickstarting with RHEL 5 i386 fails the autoreg with a "bad architecture" no matter if I attach another key or not. Manual reg using any key I wish works fine. It's like there's a hidden universal default key that wants to set the base channel to RHEL 5 x86_64. -- Bill Gunter, RHCSA | Unix Administrator | National Instruments Ireland | bill.gunter@ni.com | Ph:+353 1 247 5935 From: Paul Robert Marino <prmarino1@gmail.com> To: spacewalk-list@redhat.com Date: 17/05/2012 16:27 Subject: Re: [Spacewalk-list] registration at kickstart problem Sent by: spacewalk-list-bounces@redhat.com <hr noshade> Check if its the spacewalk default key On May 17, 2012 9:48 AM, "Bill Gunter" <<a href=mailto:bill.gunter@ni.com>bill.gunter@ni.com</a>> wrote: I recently upgraded to v1.7 postgres (from 1.0 Oracle XE via an Oracle RAC instance, yikes!) and I'm having a problem with registration at kickstart time. It's failing with this error: Traceback (most recent call last): File "/usr/sbin/rhnreg_ks", line 216, in ? cli.run() File "/usr/share/rhn/up2date_client/rhncli.py", line 65, in run sys.exit(self.main() or 0) File "/usr/sbin/rhnreg_ks", line 145, in main other = other) File "/usr/share/rhn/up2date_client/rhnreg.py", line 406, in registerSystem ret = s.registration.new_system(auth_dict) File "/usr/share/rhn/up2date_client/rhnserver.py", line 52, in __call__ raise self.__exception_from_fault(f) up2date_client.up2dateErrors.NoBaseChannelError: Error Message: Your account does not have access to any channels matching (release='5Server', arch='x86_64-redhat-linux') Error Class Code: 19 Error Class Info: Architecture and OS version combination is not supported. Explanation: An error has occurred while processing your request. If this problem persists please enter a bug report at <a href=http://bugzilla.redhat.com/ target=_blank>bugzilla.redhat.com</a>. If you choose to submit the bug report, please be sure to include details of what you were trying to do when this error occurred and details on how to reproduce this problem. The same thing also happens with an i386 version of the RHEL 5 channel. Here's the rhnreg_ks line from the kickstart file used on a sample system: rhnreg_ks --serverUrl=<a href=https://stan.natinst.com/XMLRPC target=_blank>https://stan.natinst.com/XMLRPC</a> --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-fc84976370b02471f58a0ec16c31ed70,1-dev-rhel-5-64 A manual registration using rhnreg_ks with the second key above (1-dev-rhel-5-64) works fine. How can I see what the other key (1-fc84976370b02471f58a0ec16c31ed70) points to? Thanks, Bill -- Bill Gunter, RHCSA | Unix Administrator | National Instruments Ireland | <a href=mailto:bill.gunter@ni.com target=_blank>bill.gunter@ni.com</a> | Ph:<a href=tel:%2B353%201%20247%205935 target=_blank>+353 1 247 5935</a> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target=_blank>https://www.redhat.com/mailman/listinfo/spacewalk-list</a><tt>_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com </tt><a href="https://www.redhat.com/mailman/listinfo/spacewalk-list"><tt>https://www.redhat.com/mailman/listinfo/spacewalk-list</tt></a>