[Spacewalk-list] spacewalk 0.5 ks activation key issue

Brian Kosick bkosick at mxlogic.com
Tue Jun 16 18:39:06 UTC 2009


I was looking into this, as I found the same issue... mentioned in:
http://www.mail-archive.com/spacewalk-list@redhat.com/msg01860.html

I think that there is a bug in the kickstart profile UI as well.   I had
to uncheck the "Enable Spacewalk Configuration Management" under the
kickstart->System Details.   For some reason though, if you check the
"Enable Spacewalk Remote Commands" checkbox, save, leave the page and go
back to system details, it becomes *unchecked* and "Enable Spacewalk
Config Management" is shown as selected again.  The only thing that I've
found to get around this is to leave BOTH "Enable Spacewalk Config
Management" and Enable Spacewalk Remote Commands" unchecked.


On Tue, 2009-04-21 at 04:44 -0600, John Hodrien wrote:
> On Tue, 21 Apr 2009, A.J.Delaney at brighton.ac.uk wrote:
> 
> > Dear all,
> > 	I have a spacewalk 0.5 server from which I'm trying to ks a client.  I
> > use the bare metal ks URL:
> > http://FQDN/ks/cfg/org/1/label/Fedora-11-Beta-x86_64
> > Which I note is different from the old 0.3 URL as the 0.3 URL would have
> > had a org/activation-key/label.  Using my laptop's web-browser to
> > connect to that URL gives me a permission error (which I would expect).
> > However, I get the same permission error when trying to ks a client.
> 
> Yeah, I just had the same problem.  I've only just started properly playing
> with 0.5, and I've not gone back and reviewed the mailing list properly.
> 
> > 2009-04-21 11:23:37,854 [TP-Processor1] ERROR
> > com.redhat.rhn.common.errors.PermissionExceptionHandler - Permission
> > Error
> > com.redhat.rhn.common.security.PermissionException: The activation key
> > '1-a5371e09b3eb48fb5814aba1f01b5db9' needs  provisioning capabilities to
> > be able to facilitate  the config channel functionality
> >
> > As you can see the activation key in the error message does not match
> > the activation key that was assigned to the kickstart profile.  I assume
> > that bare-metal ks clients get assigned a random activation key in order
> > to download the ks profile.  Might this key not have the requisite
> > permissions?
> >
> > This error is similar to
> > https://www.redhat.com/archives/spacewalk-list/2008-November/msg00128.html
> > However, I am using the FQDN and I believe I've correctly set up my
> > activation key.  I also have the Cobbler fix from
> > https://www.redhat.com/archives/spacewalk-list/2009-April/msg00086.html
> >
> > Any information on how to achieve kickstarting my client would be
> > appreciated.
> 
> I'm not sure about the activation key error, but I tried using the url listed
> in the cobbler config.
> 
> Take a peek in /tftpboot/pxelinux.cfg/default
> 
> The url in there doesn't require authorization.
> 
> jh
> 




More information about the Spacewalk-list mailing list