[Bug 1379591] Please test proposed package

[Adam Conrad]

Hello Sean, or anyone else affected,

Accepted lshw into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lshw/02.16-2ubuntu2.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
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