[Bug 1379591] Update Released

[Brian Murray]

The verification of the Stable Release Update for lshw has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released
Status in “lshw” source package in Utopic:
  Fix Released
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