One of them is generic (for Oracle Linux 8). The other is host-specific and is
used to rebuild the host, if triggered. It will store the last known package
configuration of that host, so if you reprovision it using Spacewalk, that
activation key will ensure the same package set is installed.
From: <spacewalk-list-boun...@redhat.com> on behalf of tommy <sz_cui...@163.com>
Reply to: "spacewalk-list@redhat.com" <spacewalk-list@redhat.com>
Date: Friday, 5 February 2021 at 6:58 pm
To: "spacewalk-list@redhat.com" <spacewalk-list@redhat.com>
Subject: [External] : Re: [Spacewalk-list] Why there are two activation keys in
my kickstart file ?
Anyone can help me ??
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> On
Behalf Of tommy
Sent: Friday, February 5, 2021 12:02 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Why there are two activation keys in my kickstart
file ?
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.
[cid:image001.jpg@01D6FC52.F293D220]
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
