Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
vendor_id information in json format added
This update adds the information about the content of all vendor_id fields in the /proc/cpuinfo file in the JavaScript Object Notation (json) format.
Description of problem:
Currently lshw provides data from the vendor_id field on x86 cpu's in xml format to match the vendor_id field in /proc/cpuinfo.
This request is to extend that ability to json output as well since json is also frequently used in hardware listing/analysis tools.
Version-Release number of selected component (if applicable):
lshw-B.02.17-4.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.lshw -class processor -quiet -json | grep -i vendor
notice we just get a vendor field, whereas requesting xml output will also provide the vendor_id field.
2.
3.
Actual results:
[root@dhcp129-184 cpu-x-check]# lshw -class processor -quiet -json | grep -i vendor
"vendor" : "Intel Corp."
Expected results:
vendor_id is included as well.
Additional info:
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Description of problem: Currently lshw provides data from the vendor_id field on x86 cpu's in xml format to match the vendor_id field in /proc/cpuinfo. This request is to extend that ability to json output as well since json is also frequently used in hardware listing/analysis tools. Version-Release number of selected component (if applicable): lshw-B.02.17-4.el6.x86_64 How reproducible: always Steps to Reproduce: 1.lshw -class processor -quiet -json | grep -i vendor notice we just get a vendor field, whereas requesting xml output will also provide the vendor_id field. 2. 3. Actual results: [root@dhcp129-184 cpu-x-check]# lshw -class processor -quiet -json | grep -i vendor "vendor" : "Intel Corp." Expected results: vendor_id is included as well. Additional info: