Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-19280

Software Updates still show applicable on the customer portal after applying them to Satellite server

XMLWordPrintable

    • 0
    • False
    • Moderate
    • None
    • None
    • None
    • None

      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,

      1. rm -f /var/lib/rhsm/cache/profile.json
      2. systemctl stop rhsmcertd
      3. 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

              jira-bugzilla-migration RH Bugzilla Integration
              jira-bugzilla-migration RH Bugzilla Integration
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: