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:
- Not all facts are listed depending on the hammer command used
Version-Release number of selected component (if applicable):
- Satellite 6.12.x
- Satellite 6.13.x
How reproducible:
Depending on the hammer command used the list of facts for a host is different. Using
"hammer --csv fact list --search "host=hostname.example.com" | grep dmi"
shows all facts related to "dmi", the command
"hammer --csv fact list | grep hostname.example.com | grep dmi"
however does not show the same list of facts.
Steps to Reproduce:
1. Run "hammer --csv fact list --search "host=hostname.example.com" | grep dmi" and save results
2. Run "hammer --csv fact list | grep hostname.example.com | grep dmi" and save the results
3. Compare the results
Actual results:
The command "hammer --csv fact list | grep hostname.example.com | grep dmi" shows a lot less facts.
Expected results:
Both commands should list the same facts
Additional info:
Example output
--------------
[root@satellite6:/root]# hammer --csv fact list | grep hostname.example.com | grep dmi
hostname.example.com,dmi::baseboard,
hostname.example.com,dmi::system,
hostname.example.com,dmi::baseboard::contained_object_handles,0
hostname.example.com,dmi::chassis::contained_elements,0
hostname.example.com,dmi::bios::bios_revision,0.0
hostname.example.com,dmi::bios::release_date,04/01/2014
hostname.example.com,dmi::chassis::oem_information,0x00000000
hostname.example.com,dmi::baseboard::chassis_handle,0x0300
hostname.example.com,dmi::memory::array_handle,0x1000
[root@satellite6:/root]# hammer --csv fact list --search "host=hostname.example.com"|grep dmi
hostname.example.com,dmi::meta,
hostname.example.com,dmi::memory,
hostname.example.com,dmi::system,
hostname.example.com,dmi::chassis,
hostname.example.com,dmi::baseboard,
hostname.example.com,dmi::processor,
hostname.example.com,dmi,
hostname.example.com,dmi::bios,
hostname.example.com,dmi::chassis::contained_elements,0
hostname.example.com,dmi::baseboard::contained_object_handles,0
hostname.example.com,dmi::bios::bios_revision,0.0
hostname.example.com,dmi::bios::release_date,04/01/2014
hostname.example.com,dmi::chassis::oem_information,0x00000000
hostname.example.com,dmi::baseboard::chassis_handle,0x0300
hostname.example.com,dmi::memory::array_handle,0x1000
hostname.example.com,dmi::bios::address,0xe8000
hostname.example.com,dmi::meta::cpu_socket_count,1
hostname.example.com,dmi::memory::number_of_devices,1
hostname.example.com,dmi::processor::thread_count,1
hostname.example.com,dmi::bios::version,1.15.0-2.module+el8.6.0+14757+c25ee005
hostname.example.com,dmi::processor::id,12 0F 80 00 FF FB 8B 07
hostname.example.com,dmi::processor::core_enabled,2
hostname.example.com,dmi::processor::core_count,2
hostname.example.com,dmi::processor::current_speed,2000 MHz
hostname.example.com,dmi::processor::max_speed,2000 MHz
hostname.example.com,dmi::memory::maximum_capacity,3078 MB
hostname.example.com,dmi::memory::size,3078 MB
hostname.example.com,dmi::bios::rom_size,64 kB
hostname.example.com,dmi::system::uuid,6D1D6DE2-C430-4C70-9831-D268C04F1738
hostname.example.com,dmi::system::sku_number,8.6.0
hostname.example.com,dmi::system::version,8.6-0.1.el8
hostname.example.com,dmi::bios::runtime_size,96 kB
hostname.example.com,dmi::baseboard::features,Board is a hosting board
hostname.example.com,dmi::processor::type,Central Processor
hostname.example.com,dmi::processor::socket_designation,CPU 0
hostname.example.com,dmi::memory::form_factor,DIMM
hostname.example.com,dmi::memory::locator,DIMM 0
hostname.example.com,dmi::system::serial_number,e18c8687-a6e8-9512-ab7c-2cf05d8c16c9
hostname.example.com,dmi::baseboard::type,Motherboard
hostname.example.com,dmi::memory::error_correction_type,Multi-bit ECC
hostname.example.com,dmi::memory::set,None
hostname.example.com,dmi::processor::characteristics,None
hostname.example.com,dmi::chassis::lock,Not Present
hostname.example.com,dmi::processor::l2_cache_handle,Not Provided
hostname.example.com,dmi::processor::l3_cache_handle,Not Provided
hostname.example.com,dmi::memory::error_information_handle,Not Provided
hostname.example.com,dmi::processor::l1_cache_handle,Not Provided
hostname.example.com,dmi::memory::type_detail,Other
hostname.example.com,dmi::processor::family,Other
hostname.example.com,dmi::chassis::type,Other
hostname.example.com,dmi::memory::location,Other
hostname.example.com,dmi::processor::upgrade,Other
hostname.example.com,dmi::processor::status,"Populated, Enabled"
hostname.example.com,dmi::system::wake-up_type,Power Switch
hostname.example.com,dmi::memory::type,RAM
hostname.example.com,dmi::memory::manufacturer,Red Hat
hostname.example.com,dmi::processor::manufacturer,Red Hat
hostname.example.com,dmi::baseboard::manufacturer,Red Hat
hostname.example.com,dmi::system::manufacturer,Red Hat
hostname.example.com,dmi::chassis::manufacturer,Red Hat
hostname.example.com,dmi::system::product_name,RHEL
hostname.example.com,dmi::baseboard::version,"RHEL-8.6.0 PC (Q35 + ICH9, 2009)"
hostname.example.com,dmi::chassis::version,"RHEL-8.6.0 PC (Q35 + ICH9, 2009)"
hostname.example.com,dmi::processor::version,"RHEL-8.6.0 PC (Q35 + ICH9, 2009)"
hostname.example.com,dmi::baseboard::product_name,RHEL-AV
hostname.example.com,dmi::system::family,RHV
hostname.example.com,dmi::chassis::power_supply_state,Safe
hostname.example.com,dmi::chassis::boot-up_state,Safe
hostname.example.com,dmi::chassis::thermal_state,Safe
hostname.example.com,dmi::bios::vendor,SeaBIOS
hostname.example.com,dmi::memory::use,System Memory
I'm not observing this on 6.13.1.
# hammer --csv fact list | grep ultimate-bat | grep dmi | wc -l
51
# hammer --csv fact list --search 'host=ultimate-bat.example.com' | grep dmi | wc -l
51
# hammer --csv fact list | grep ultimate-bat | wc -l
153
# hammer --csv fact list --search 'host=ultimate-bat.example.com' | wc -l
154
When listing all facts, the grep variant filters out the header so it has one less line.
As far as I know hammer just shows whatever the api gives it so I'll pass this on to fact component for further investigation.
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.