Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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'
~~~
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.
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' ~~~