Project

General

Profile

Actions

Bug #37184

closed

Satellite "Registered Content Hosts" report generates incorrect hosts' kernel version

Added by Hao Yu 2 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Reporting
Target version:
-
Fixed in Releases:
Found in Releases:

Description

Cloned from bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2265062

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'

Actions #1

Updated by Hao Yu 2 months ago

  • Description updated (diff)
Actions #2

Updated by The Foreman Bot 2 months ago

  • Status changed from New to Ready For Testing
  • Assignee set to Hao Yu
  • Pull request https://github.com/theforeman/foreman/pull/10056 added
Actions #3

Updated by The Foreman Bot about 2 months ago

  • Fixed in Releases 3.11.0 added
Actions #4

Updated by Hao Yu about 2 months ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by The Foreman Bot about 1 month ago

  • Pull request https://github.com/theforeman/foreman/pull/10103 added
Actions #6

Updated by The Foreman Bot about 1 month ago

  • Fixed in Releases 3.10.0 added
Actions

Also available in: Atom PDF