Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-23407 Satellite "Registered Content Hosts" report generates incorrect hosts' kernel version
  3. SAT-26419

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

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Reporting
    • Sprint 136, Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141

      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.
      ~~~

      1. /usr/share/foreman/app/models/host/base.rb
        module Host
        class Base < ApplicationRecord
        <snip>
        has_one :kernel_release, ->
        Unknown macro: { joins(}

        , :class_name => '::FactValue', :foreign_key => 'host_id'
        ~~~

      QE Tracker for https://issues.redhat.com/browse/SAT-23407
      Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2265062

            rh-ee-damoore David Moore
            satellite-jira-automation@redhat.com Satellite Jira-Automation
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: