[Spacewalk-list] registration at kickstart problem

Sun May 27 08:53:59 UTC 2012

Colin
That's a different issue. What's happening is the activation key is getting
swapped to the spacewalk default key. There are two ways to handle that
there is a default option that tells it to reset the activation key on
kickstart can be modified. This default behavior will be reversed in
version 1.8 so this issue should go away for most users. The other way to
handle it is to distrobution channel map I wrote a script some time ago to
do that for you. ill send you links to tickets that explain your issue and
how to workaround it on monday.
On May 27, 2012 4:15 AM, "Colin Coe" <colin.coe at gmail.com> wrote:

> I see this when attempting to re-provision a VM by simply kickstarting
> the VM.  If I delete the VM's record first then I don't see this
> message.
>
> CC
>
> On Sun, May 27, 2012 at 2:43 PM, Paul Robert Marino <prmarino1 at gmail.com>
> wrote:
> > Probably you are accidentaly loading the 64 bit kernel and or initrd
> instead
> > of the 32 bit one.
> >
> > On May 24, 2012 6:22 AM, "Bill Gunter" <bill.gunter at ni.com> wrote:
> >>
> >> 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 at ni.com  | Ph:+353 1 247 5935
> >>
> >>
> >>
> >> From:        Paul Robert Marino <prmarino1 at gmail.com>
> >> To:        spacewalk-list at redhat.com
> >> Date:        17/05/2012 16:27
> >> Subject:        Re: [Spacewalk-list] registration at kickstart problem
> >> Sent by:        spacewalk-list-bounces at redhat.com
> >> ________________________________
> >>
> >>
> >>
> >> Check if its the spacewalk default key
> >>
> >> On May 17, 2012 9:48 AM, "Bill Gunter" <bill.gunter at ni.com> 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 bugzilla.redhat.com.
> >>     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=https://stan.natinst.com/XMLRPC
> >> --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
> |
> >> bill.gunter at ni.com  | Ph:+353 1 247 5935
> >> _______________________________________________
> >> Spacewalk-list mailing list
> >> Spacewalk-list at redhat.com
> >>
> >>
> https://www.redhat.com/mailman/listinfo/spacewalk-list_______________________________________________
> >> Spacewalk-list mailing list
> >> Spacewalk-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/spacewalk-list
> >>
> >>
> >> _______________________________________________
> >> Spacewalk-list mailing list
> >> Spacewalk-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/spacewalk-list
> >
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
> --
> RHCE#805007969328369
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120527/4abf5e16/attachment.htm>