[Bug 1379591] Re: Moonshot nodes with Mellanox interfaces fail to deploy in maas 1.7

[dann frazier]

Fix verified:

ubuntu at ms01a:~$ sudo dpkg -i lshw_02.16-2ubuntu1.1_arm64.deb 
dpkg: warning: downgrading lshw from 02.16-2ubuntu1.2 to 02.16-2ubuntu1.1
(Reading database ... 80719 files and directories currently installed.)
Preparing to unpack lshw_02.16-2ubuntu1.1_arm64.deb ...
Unpacking lshw (02.16-2ubuntu1.1) over (02.16-2ubuntu1.2) ...
Setting up lshw (02.16-2ubuntu1.1) ...
Processing triggers for man-db (2.6.7.1-1) ...
ubuntu at ms01a:~$ sudo lshw -class net > pre-fix
ubuntu at ms01a:~$ sudo dpkg -i lshw_02.16-2ubuntu1.2_arm64.deb 
(Reading database ... 80719 files and directories currently installed.)
Preparing to unpack lshw_02.16-2ubuntu1.2_arm64.deb ...
Unpacking lshw (02.16-2ubuntu1.2) over (02.16-2ubuntu1.1) ...
Setting up lshw (02.16-2ubuntu1.2) ...
Processing triggers for man-db (2.6.7.1-1) ...
ubuntu at ms01a:~$ sudo lshw -class net > post-fix
ubuntu at ms01a:~$ diff -u pre-fix post-fix 
--- pre-fix	2014-11-04 11:23:20.564933999 -0500
+++ post-fix	2014-11-04 11:23:36.674933999 -0500
@@ -1,4 +1,4 @@
-  *-network
+  *-network DISABLED
        description: Ethernet interface
        product: MT27500 Family [ConnectX-3]
        vendor: Mellanox Technologies
@@ -11,7 +11,7 @@
        width: 64 bits
        clock: 33MHz
        capabilities: pm vpd msix pciexpress bus_master cap_list ethernet physical tp
-       configuration: autonegotiation=off broadcast=yes driver=mlx4_en driverversion=2.2-1 (Feb 2014) duplex=full firmware=2.30.3000 ip=10.229.41.200 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
+       configuration: autonegotiation=off broadcast=yes driver=mlx4_en driverversion=2.2-1 (Feb 2014) duplex=full firmware=2.30.3000 latency=0 link=no multicast=yes port=twisted pair speed=1Gbit/s
        resources: irq:244 memory:a010800000-a0108fffff memory:a010000000-a0107fffff
   *-network:0
        description: Ethernet interface
@@ -32,14 +32,23 @@
   *-network:2
        description: Ethernet interface
        physical id: 3
+       bus info: pci at 0000:01:00.0
+       logical name: eth0
+       serial: 2c:59:e5:36:9a:b2
+       size: 1Gbit/s
+       capabilities: ethernet physical tp
+       configuration: autonegotiation=off broadcast=yes driver=mlx4_en driverversion=2.2-1 (Feb 2014) duplex=full firmware=2.30.3000 ip=10.229.41.200 link=yes multicast=yes port=twisted pair speed=1Gbit/s
+  *-network:3
+       description: Ethernet interface
+       physical id: 4
        logical name: vnet1
        serial: fe:16:3e:fe:b1:a1
        size: 10Mbit/s
        capabilities: ethernet physical
        configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=yes multicast=yes port=twisted pair speed=10Mbit/s
-  *-network:3
+  *-network:4
        description: Ethernet interface
-       physical id: 4
+       physical id: 5
        logical name: novatap
        serial: 46:df:52:39:2e:34
        size: 10Mbit/s


** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lshw in Ubuntu.
https://bugs.launchpad.net/bugs/1379591

Title:
  Moonshot nodes with Mellanox interfaces fail to deploy in maas 1.7

Status in lshw - Hardware Lister:
  Unknown
Status in MAAS:
  Won't Fix
Status in “lshw” package in Ubuntu:
  Fix Released
Status in “lshw” source package in Trusty:
  Fix Committed
Status in “lshw” source package in Utopic:
  Fix Committed
Status in “lshw” source package in Vivid:
  Fix Released
Status in “lshw” package in Debian:
  New

Bug description:
  [Impact]
  On systems with multiple NICs on a single PCI function, lshw will fail to show all of the NICs, and might associate the wrong MAC with an interface. This is known to cause problems with MAAS functioning on such systems.
  [Test Case]
  Run lshw on a system with >1 NIC on a PCI function and observe the output.
  [Regression Risk]
  The cause of this issue is some deduplication code in lshw that checks to see if the NIC it is scanning has already been registered. The included solution is to also compare the MACs before assuming it is the same NIC. So, regression risk could be that this code is broken (e.g. segfaults) or that there is a real world case where multiple NICs may have the same MAC (hardware bridge?).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lshw/+bug/1379591/+subscriptions