Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694905 - hardware-detect fails on ppc64le due to KeyError
Summary: hardware-detect fails on ppc64le due to KeyError
Keywords:
Status: ON_DEV
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-hardware
Version: 15.0 (Stein)
Hardware: ppc64le
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Tony Breeds
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1667964 1698308
TreeView+ depends on / blocked
 
Reported: 2019-04-02 02:42 UTC by Tony Breeds
Modified: 2019-04-12 04:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1698308 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Tony Breeds 2019-04-02 02:42:48 UTC
Description of problem:  hardware-detect is failing due to:

---
Vendor ID isn't in the lscpu output:

[root@ibm-p9wr-13 ~]# LANG=en_US.UTF-8 lscpu -x
Architecture:        ppc64le
Byte Order:          Little Endian
CPU(s):              144
On-line CPU(s) mask: ffffffffffffffffffffffffffffffffffff
Thread(s) per core:  4
Core(s) per socket:  18
Socket(s):           2
NUMA node(s):        6
Model:               2.2 (pvr 004e 1202)
Model name:          POWER9, altivec supported
CPU max MHz:         3800.0000
CPU min MHz:         2300.0000
L1d cache:           32K
L1i cache:           32K
L2 cache:            512K
L3 cache:            10240K
NUMA node0 CPU(s):   ffffffffffffffffff
NUMA node8 CPU(s):   ffffffffffffffffff000000000000000000
NUMA node252 CPU(s): 0
NUMA node253 CPU(s): 0
NUMA node254 CPU(s): 0
NUMA node255 CPU(s): 0
Which causes

[root@ibm-p9wr-13 ~]# hardware-detect
/bin/sh: cli64: command not found
Info: detect_areca: No controller found
Cannot find megacli on the system
read_smart: Reading S.M.A.R.T information on /dev/sdb
read_smart_ata: Found S.M.A.R.T information on /dev/sdb
read_smart: Reading S.M.A.R.T information on /dev/sda
read_smart_ata: Found S.M.A.R.T information on /dev/sda
connect: Connection refused 
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
connect: Connection refused
Failed to connect to lldpad - clif_open: Connection refused
Traceback (most recent call last):
  File "/usr/bin/hardware-detect", line 10, in <module>
    sys.exit(main())
  File "/usr/lib/python3.6/site-packages/hardware/detect.py", line 997, in main
    _main(options)
  File "/usr/lib/python3.6/site-packages/hardware/detect.py", line 924, in _main
    if not detect_system(hrdw):
  File "/usr/lib/python3.6/site-packages/hardware/detect.py", line 666, in detect_system
    get_cpus(hw_lst)
  File "/usr/lib/python3.6/site-packages/hardware/detect.py", line 725, in get_cpus
    processor), 'vendor', lscpu['Vendor ID']))
KeyError: 'Vendor ID'
[root@ibm-p9wr-13 ~]# 
---
Version-Release number of selected component (if applicable):
python3-hardware-0.20.0-0.20190328181231.b417976.el8ost.noarch



How reproducible:
100%


Steps to Reproduce:
1. Install python3-hardware on a ppc64le system running rhel-8
2. run hardware-detect


Note You need to log in before you can comment on or make changes to this bug.