Hide Forgot
Description of problem: The /distribution/inventory task is not populating the MAC address for HP Moonshot m400 systems. The lshw command lists the MAC address, but the inventory task is not seeing it. For example: [root@hp-moonshot-c40 ~]# ip link list 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000 link/ether 14:58:d0:58:55:52 brd ff:ff:ff:ff:ff:ff 3: eno1d1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000 link/ether 14:58:d0:58:55:53 brd ff:ff:ff:ff:ff:ff [root@hp-moonshot-c40 ~]# lshw ... *-network description: Ethernet interface physical id: 1 bus info: pci@0000:01:00.0 logical name: eno1 serial: 14:58:d0:58:55:52 size: 10Gbit/s capabilities: ethernet physical autonegotiation configuration: autonegotiation=on broadcast=yes driver=mlx4_en driverversion=2.2-1 (Feb 2014) duplex=full firmware=2.35.5100 ip=192.168.1.40 link=yes multicast=yes speed=10Gbit/s [root@hp-moonshot-c40 ~]# rpm -q lshw lshw-B.02.18-0.2.20150722svn2580.beaker.5.1.el7.aarch64 But after running /distribution/inventory, the MAC address field is empty in the Beaker database: ~]$ bkr system-details hp-moonshot-c40 | grep macAddress ~]$ Version-Release number of selected component (if applicable): beaker-distribution-inventory-1.2-8.noarch lshw-B.02.18-0.2.20150722svn2580.beaker.5.1.el7.aarch64 How reproducible: always Steps to Reproduce: 1. run /distribution/inventory on an HP Moonshot m400 system 2. check Beaker System Details for the MAC address Actual results: MAC address is blank Expected results: MAC address is populated Additional info:
(In reply to Jeff Bastian from comment #0) > Version-Release number of selected component (if applicable): > beaker-distribution-inventory-1.2-8.noarch > lshw-B.02.18-0.2.20150722svn2580.beaker.5.1.el7.aarch64 One more: beaker-system-scan-2.2-1.el7_2.aarch64
It actually doesn't populate the MAC address anywhere at all. I'm not sure why... maybe just in case there is more than one NIC and the script doesn't know which one should be stored in Beaker. But in that case, surely just the first linked interface should be fine. Like vendor/model we would make sure it doesn't overwrite any existing value already stored in Beaker, so that admins can correct it if necessary.