-
Feature Request
-
Resolution: Unresolved
-
None
-
6.11.0
Description of problem:
Another useful data coming from the facts should be added. Namely
- serial number
- product name
- manufacturer
- CPU model
I'd like to see those as new columns on the Host index page as well as detail page. They should not be read directly from facts but rather should be implemented as reported data.
Value sources
subscription-manager: dmi.baseboard.serial_number
puppet: dmi:board:serial_number
ansible: ansible_board_serial
subscription-manager: dmi.baseboard.product_name
puppet: dmi:board:product_name
ansible: ansible_board_name
subscription-manager: dmi.baseboard.manufacturer
puppet: dmi:board:manufacturer
ansible: ansible_board_vendor
subscription-manager: dmi.processor.version or lscpu.model_name or proc_cpuinfo.common.model_name (the last is probably the best)
puppet: processors:models (first value)
ansible: ansible_processor[2]
I should also be able to search by these values.
[SAT-18347] [RFE] As a user I'd like to see additional reported data for the hosts
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.
Brad Buckingham
added a comment - - edited Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration. Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Brad Buckingham
added a comment - - edited Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you. 
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@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information.