[Spacewalk-list] [External] : Re: Why there are two activation keys in my kickstart file ?
tommy
sz_cuitao at 163.com
Tue Feb 9 02:07:35 UTC 2021
Yes, only spacewalk managed repos are enabled.
[root at testol83 ~]# yum repolist -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync, spacewalk
initialized Spacewalk plugin
This system is receiving updates from Unbreakable Linux Network or Spacewalk.
YUM version: 4.2.23
cachedir: /var/cache/dnf
Last metadata expiration check: 2:12:36 ago on Tue 09 Feb 2021 07:52:13 AM CST.
Repo-id : ol8_uekr6
Repo-name : OL8_UEKR6
Repo-updated : Tue 09 Feb 2021 04:38:26 AM CST
Repo-pkgs : 178
Repo-available-pkgs: 178
Repo-size : 2.4 G
Repo-baseurl : https://olms1.tltd.com/XMLRPC/GET-REQ/ol8_uekr6
Repo-expire : 172,800 second(s) (last: Tue 09 Feb 2021 07:52:12 AM CST)
Repo-id : oracle_linux_8_addons
Repo-name : Oracle_Linux_8_Addons
Repo-updated : Tue 09 Feb 2021 04:38:32 AM CST
Repo-pkgs : 71
Repo-available-pkgs: 71
Repo-size : 55 M
Repo-baseurl : https://olms1.tltd.com/XMLRPC/GET-REQ/oracle_linux_8_addons
Repo-expire : 172,800 second(s) (last: Tue 09 Feb 2021 07:52:13 AM CST)
Repo-id : oracle_linux_8_appstream
Repo-name : Oracle_Linux_8_AppStream
Repo-updated : Tue 09 Feb 2021 04:06:25 AM CST
Repo-pkgs : 15,833
Repo-available-pkgs: 14,095
Repo-size : 36 G
Repo-baseurl : https://olms1.tltd.com/XMLRPC/GET-REQ/oracle_linux_8_appstream
Repo-expire : 172,800 second(s) (last: Tue 09 Feb 2021 07:52:12 AM CST)
Repo-id : oracle_linux_8_baseos
Repo-name : Oracle_Linux_8_BaseOS
Repo-updated : Tue 09 Feb 2021 04:01:32 AM CST
Repo-pkgs : 6,680
Repo-available-pkgs: 6,677
Repo-size : 9.2 G
Repo-baseurl : https://olms1.tltd.com/XMLRPC/GET-REQ/oracle_linux_8_baseos
Repo-expire : 172,800 second(s) (last: Tue 09 Feb 2021 07:52:12 AM CST)
Total packages: 22,762
[root at testol83 ~]#
[root at testol83 ~]#
[root at testol83 ~]#
[root at testol83 ~]#
[root at testol83 ~]# yum repolist all
This system is receiving updates from Unbreakable Linux Network or Spacewalk.
repo id repo name status
ol8_UEKR6 Latest Unbreakable Enterprise Kernel Release 6 for Oracle Linux 8 (x86_64) disabled
ol8_UEKR6_RDMA Oracle Linux 8 UEK6 RDMA (x86_64) disabled
ol8_addons Oracle Linux 8 Addons (x86_64) disabled
ol8_appstream Oracle Linux 8 Application Stream (x86_64) disabled
ol8_baseos_latest Oracle Linux 8 BaseOS Latest (x86_64) disabled
ol8_codeready_builder Oracle Linux 8 CodeReady Builder (x86_64) - Unsupported disabled
ol8_u0_baseos_base Oracle Linux 8 BaseOS GA (x86_64) disabled
ol8_u1_baseos_base Oracle Linux 8.1 BaseOS (x86_64) disabled
ol8_u2_baseos_base Oracle Linux 8.2 BaseOS (x86_64) disabled
ol8_u3_baseos_base Oracle Linux 8.3 BaseOS (x86_64) disabled
ol8_uekr6 OL8_UEKR6 enabled
oracle_linux_8_addons Oracle_Linux_8_Addons enabled
oracle_linux_8_appstream Oracle_Linux_8_AppStream enabled
oracle_linux_8_baseos Oracle_Linux_8_BaseOS enabled
[root at testol83 ~]#
[root at testol83 ~]#
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> On Behalf Of Avi Miller
Sent: Tuesday, February 9, 2021 4:11 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] [External] : Re: Why there are two activation keys in my kickstart file ?
Hey,
That key is system-specific and managed by Spacewalk, and it allows Spacewalk to reprovision this specific server.
Out of curiousity, what happens if you run "dnf update" on the server? It's probably worth running "dnf repolist -v" on that server to ensure that only the Spacewalk-managed repos are enabled and the yum.oracle.com ones are not.
Just a note that you should always sync the entire repo for OL8. Using the --latest parameter (or checking the box in the UI) will break the modular metadata. We mention this in our docs too: https://docs.oracle.com/en/operating-systems/oracle-linux-manager/2.10/admin/chap-chan-repo.html#syncswcsrs
Thanks,
Avi
From: <spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> > on behalf of tommy <sz_cuitao at 163.com <mailto:sz_cuitao at 163.com> >
Reply to: "spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> " <spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> >
Date: Monday, 8 February 2021 at 10:09 pm
To: "spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> " <spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> >
Subject: Re: [Spacewalk-list] [External] : Re: Why there are two activation keys in my kickstart file ?
1. I have named the activation key like this, but one key that appears in the kickstart not in the list, I don’t know where it comes from and why should it exists((1-fd833f6fb24dbd1f8807f36d434049a4).
2. If you click on the "143" in the table, does Spacewalk provide a list of the packages?
No, there’s no package list, like this:
But , If I first choose the testol83 then select the manage and then press upgrade, there are packages needs upgrade like below:
3. I tried the command, but it still exists.
[root at testol83 ~]# rhn-profile-sync -v
Updating package profile...
Updating hardware profile...
From: spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> <spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> > On Behalf Of Avi Miller
Sent: Monday, February 8, 2021 4:30 AM
To: spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] [External] : Re: Why there are two activation keys in my kickstart file ?
First, I strongly encourage you to name your activation keys instead of using the ones Spacewalk auto-generates. It makes it a lot easier for troubleshooting. :)
Second, that inconsistency is interesting because there are no errata associated with the 143 packages that Spacewalk thinks are available. If you click on the "143" in the table, does Spacewalk provide a list of the packages? I would also suggest manually running "rhn-profile-sync -v" on testol83.tltd.com to see if that resolves the inconsistency.
From: <spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> > on behalf of tommy <sz_cuitao at 163.com <mailto:sz_cuitao at 163.com> >
Reply to: "spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> " <spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> >
Date: Saturday, 6 February 2021 at 10:23 pm
To: "spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> " <spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> >
Subject: Re: [Spacewalk-list] [External] : Re: Why there are two activation keys in my kickstart file ?
1.You mean that 1-296a3f05d95aec9f804024a596acc810 is host-specific one and (1-fd833f6fb24dbd1f8807f36d434049a4 is generic ?
2.In my env, there is a problem maybe related to the above question:
One os which registered with 1-296a3f05d95aec9f804024a596acc810 appears that there are 143 packages needs update as below:
But when select the system, you find that the system is up to date like below:
Why ???
Thanks.
From: spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> <spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> > On Behalf Of Avi Miller
Sent: Saturday, February 6, 2021 3:40 AM
To: spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] [External] : Re: Why there are two activation keys in my kickstart file ?
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-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> > on behalf of tommy <sz_cuitao at 163.com <mailto:sz_cuitao at 163.com> >
Reply to: "spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> " <spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> >
Date: Friday, 5 February 2021 at 6:58 pm
To: "spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> " <spacewalk-list at redhat.com <mailto:spacewalk-list at redhat.com> >
Subject: [External] : Re: [Spacewalk-list] Why there are two activation keys in my kickstart file ?
Anyone can help me ??
From: spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> <spacewalk-list-bounces at redhat.com <mailto:spacewalk-list-bounces at redhat.com> > On Behalf Of tommy
Sent: Friday, February 5, 2021 12:02 PM
To: spacewalk-list at redhat.com <mailto:spacewalk-list at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.jpg
Type: image/jpeg
Size: 34552 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 34762 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.jpg
Type: image/jpeg
Size: 82470 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.jpg
Type: image/jpeg
Size: 18781 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.jpg
Type: image/jpeg
Size: 32201 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.jpg
Type: image/jpeg
Size: 53722 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.jpg
Type: image/jpeg
Size: 34804 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.jpg
Type: image/jpeg
Size: 43197 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210209/c979ac56/attachment-0007.jpg>
More information about the Spacewalk-list
mailing list