[Spacewalk-list] Why there are two activation keys in my kickstart file ?
tommy
sz_cuitao at 163.com
Fri Feb 5 04:02:02 UTC 2021
Hi ,everyone:
This is part of the kickstart which is auto produced by spacewalk.
try: # python 2
import xmlrpclib
except ImportError: # python 3
import xmlrpc.client as xmlrpclib
import shutil
import sys
import os.path
try:
old_system_id = "/tmp/rhn/systemid"
new_system_id = "/mnt/sysimage/root/systemid.old"
tmp_key = "/mnt/sysimage/tmp/key"
new_keys =
"1-fd833f6fb24dbd1f8807f36d434049a4,1-296a3f05d95aec9f804024a596acc810"
for key in new_keys.split(','):
if key.startswith('re-'):
sys.exit(0)
You can see that there are tow keys, but when I create the kickstart, I only
choose one key(1-296a3f05d95aec9f804024a596acc810) just like below pic, and
the other one(1-fd833f6fb24dbd1f8807f36d434049a4) does not exists in my
spacewalk system.
But why the spacewalk produce such a kickstart file ? Why ?
Could you give me some explain ?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210205/2f4e9fe1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 43963 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210205/2f4e9fe1/attachment.jpg>
More information about the Spacewalk-list
mailing list