On Mon, 2009-08-10 at 16:50 -0500, Mike McCune wrote: > every kickstart profile in Spacewalk has a default activation key > used > with it, the 1st one you are seeing is the one associated with the > profile, the 2nd is your custom key. > > Mike
Hmmm... ok then. Any idea why I can't get the system registered using the registration string in the kickstart, which includes both keys, ala: rhnreg_ks --serverUrl=https://<myserver>/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-28ef2e19220231062d6ab036e00ddf38,1-037880d329934283fd3264f97aa33317 The above string is what I see in my kickstart when I look at it via the UI, however, if I look at the "cobbler.ks" file on the system after it installs, the "other" activation key in the command above is completely different... as if it's being generated randomly for each build. ala: rhnreg_ks --serverUrl=https://<myserver>/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-037880d329934283fd3264f97aa33317,1-bc356b33a64a3b6c422a35a9bc019a7d Either way, I don't seem to be able to register until I remove the "other" key and use just my chosen activation key. Any thoughts? I'm confused. Andy
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
