Description of problem: The "Host - Registered Content Hosts" is not showing the correct latest kernel available. Host is on 7.7 and currently using kernel 3.10.0-1062.18.1.el7. The host has access to kernel 3.10.0-1062.49.1.el7, yet the "Registered Content Hosts" report is showing the latest available kernel to be 3.10.0-1062.40.1.el7. From the command line with yum, the host is showing it has access to 3.10.0-1062.49.1.el7 kernel. Also, from the Satellite UI, navigating to the content host and selecting the Errata tab, the latest errata for the kernel that this host has access to, also shows 3.10.0-1062.49.1.el7. Version-Release number of selected component (if applicable): Red Hat Satellite 6.8 Red Hat Enterprise Linux Server 7.7 with EUS How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Report shows 1062.40.1.el7 as latest kernel. Expected results: Report shows 1062.49.1.el7 as the latest kernel. Additional info:
The report information is based on Satellite DB, more specifically we look at applicable RPMs with the name "kernel", order it by version and pick one. There could be 2 causes, either Satellite DB does not have the newest package availability information or more version are available and we report the wrong one. Could you please ask customer to perform the following foreman-rake console puts Host.find_by_name('$fqdn').applicable_rpms.where(name: 'kernel').order(:version_sortable).map(&:nvra) exit Please substitute $fqdn with the FQDN of the host that is affected. My assumption is we'll see the list in a wrong order (the first one of the list is used in the report). If that's the case, it's a bug in the ordering.
Hi Marek, Thanks for the quick response. Your assumption was correct. Here is the output from that command: [root@satellite ~]# foreman-rake console Loading production environment (Rails 6.0.3.4) irb(main):001:0> puts Host.find_by_name('host.example.com').applicable_rpms.where(name: 'kernel').order(:version_sortable).map(&:nvra) kernel-3.10.0-1062.40.1.el7.x86_64 kernel-3.10.0-1062.37.1.el7.x86_64 kernel-3.10.0-1062.49.1.el7.x86_64 kernel-3.10.0-1062.46.1.el7.x86_64 kernel-3.10.0-1062.30.1.el7.x86_64 kernel-3.10.0-1062.33.1.el7.x86_64 kernel-3.10.0-1062.43.1.el7.x86_64 kernel-3.10.0-1062.26.1.el7.x86_64 kernel-3.10.0-1062.31.2.el7.x86_64 kernel-3.10.0-1062.31.3.el7.x86_64 kernel-3.10.0-1062.21.1.el7.x86_64 kernel-3.10.0-1062.36.1.el7.x86_64 kernel-3.10.0-1062.45.1.el7.x86_64 => nil Kind regards,
I'm moving this to another component, this is not specific to the reporting. The ordering by "version_sortable" does not work. Given this is done on applicable rpms, moving to Host - Content, please reassing if there's a better one.
Created redmine issue https://projects.theforeman.org/issues/35040 from this bug
Upstream bug assigned to iballou
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35040 has been resolved.
Verified Version Tested: 6.12.0 snap 13 Results: The latest kernel version is correctly displayed in the UI and CLI as well as in the "Registered Content Hosts" report.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:8506