Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBenjamin Kielhold
2023-02-27 22:27:32 UTC
Created attachment 1946793[details]
Attachment shows an example of an advisory (RHSA-2023:0832) still needing to be installed/applied to the server
Greetings,
Description of problem:
----
After updating packages for Satellite server using `satellite-maintain packages update`, applicable `Software Updates` are still present at access.redhat.com/management/systems/<UUID> even after waiting 4 hours to 24 hours and forcing the server to checkin via the guidance provided on the page.
Executing, `yum updateinfo list security --installed` on the server will show that the security advisories have been applied yet are still referenced needing to be applied on access.redhat.com/management/systems/<UUID> .
Version-Release number of selected component (if applicable):
----
Candlepin: candlepin-4.1.19-1.el8sat.noarch
Satellite: satellite-6.12.2-1.el8sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Access access.redhat.com/management/systems/<UUID> for the server that has applicable software updates and view what is ready and waiting to be installed.
2. Install those applicable updates -- Ex:`satellite-maintain packages update`
3. Force a checkin using the recommended way shown via the "?" next to `Software Updates` text. Link: https://access.redhat.com/solutions/3210391
~~~
If the RHEL version 7.7 or greater,
# rm -f /var/lib/rhsm/cache/profile.json
# systemctl stop rhsmcertd
# rhsmcertd --now
~~~
and wait 4 hours or more per the guidance.
4. Once again view access.redhat.com/management/systems/<UUID> and see the applicable installs still available.
5. Execute, `yum updateinfo list security --installed` and compare to verify that the software was installed.
Actual results:
----
[root@satellite612]# yum updateinfo list security --installed -v | grep "RHSA-2023:0832"
RHSA-2023:0832 Important/Sec. kernel-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
RHSA-2023:0832 Important/Sec. kernel-core-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
RHSA-2023:0832 Important/Sec. kernel-headers-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
RHSA-2023:0832 Important/Sec. kernel-modules-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
RHSA-2023:0832 Important/Sec. kernel-modules-extra-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
RHSA-2023:0832 Important/Sec. kernel-tools-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
RHSA-2023:0832 Important/Sec. kernel-tools-libs-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
RHSA-2023:0832 Important/Sec. python3-perf-4.18.0-425.13.1.el8_7.x86_64 2023-02-21 03:46:19
[root@satellite612] # uname -r
4.18.0-425.13.1.el8_7.x86_64
See Attachment, `ExampleApplicable.png` showing that the above is still needing to be applied. See the last checkin day as Feb 27th for the server used in example and the install date was 2023-02-21.
[root@satellite612] # yum updateinfo list updates security | grep "RHSA-2023:0832"
The above command returns nothing needing to be applied.
Expected results:
----
After the server checks in, expected result would be that it would correctly be reflected what software updates were needing to be applied.
Respectfully,
Benjamin Kielhold