This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2265062 - Satellite "Registered Content Hosts" report generates incorrect hosts' kernel version
Summary: Satellite "Registered Content Hosts" report generates incorrect hosts' kernel...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.14.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Hao Chang Yu
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-20 06:21 UTC by Hao Chang Yu
Modified: 2024-06-06 17:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:03:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37184 0 Normal New Satellite "Registered Content Hosts" report generates incorrect hosts' kernel version 2024-02-20 06:29:27 UTC
Red Hat Issue Tracker   SAT-23407 0 None Migrated None 2024-06-06 17:03:27 UTC

Description Hao Chang Yu 2024-02-20 06:21:36 UTC
Description of problem:
Old or incorrect host kernel versions are printed in the generated report.

Multiple services are reporting kernel version facts to the Satellite, such as Ansible, Puppet and RHSM. While resolving the kernel version for a host, Satellite will pick the first one order by fact type. Since "Ansible" starts with 'A', kernel version reported by Ansible will normally be picked. If Ansible roles job is not run after the last host kernel update, then old or wrong kernel version will be reported.

How reproducible:
Easy

Steps to Reproduce:
1. Register a host to the Satellite.
2. Run Ansible roles against the host
3. Update the kernel of the host

Actual results:
Report template generated the old kernel version of the host.

Expected results:
Report template generated the upgraded kernel version of the host.


Additional info:

We can run the following hammer command to query all reported kernel versions of a host.
~~~
hammer fact list --search "host = content_host.example.com and (name = kernelrelease or name = ansible_kernel or name = kernel::release or name = uname::release)"
~~~

As we can see in the example below, Ansible fact has the outdated kernel version.
~~~
----------------------------|----------------|-----------------------------
HOST                        | FACT           | VALUE
----------------------------|----------------|-----------------------------
content_host.example.com    | ansible_kernel | 3.10.0-1062.4.1.el7.x86_64  <==============
content_host.example.com    | uname::release | 3.10.0-1160.105.1.el7.x86_64
----------------------------|----------------|-----------------------------
~~~


As we can see below, the results are sorted by "fact_names.type" which means Ansible fact type always took precedence over other fact types.
~~~
# /usr/share/foreman/app/models/host/base.rb
module Host
  class Base < ApplicationRecord
    <snip>
    has_one :kernel_release, -> { joins(:fact_name).where({ 'fact_names.name' => KERNEL_RELEASE_FACTS }).order('fact_names.type') }, :class_name => '::FactValue', :foreign_key => 'host_id'
~~~

Comment 2 Bryan Kearney 2024-02-26 12:03:42 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37184 has been resolved.

Comment 3 Eric Helms 2024-06-06 17:03:29 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.