Collect and report more information from real interfaces for debugging purpose

Bug #2018959 reported by DUFOUR Olivier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-magpie
Triaged
Wishlist
Unassigned

Bug Description

For the sake of building more in-depth reports, especially on the network side, since many issues can be the root cause of a lot of trouble. Collecting more information about the involved network interfaces from the server hosting the test can help greatly.

It would be helpful to retrieve the following information :
1) in the case of a bond, or a bridge, or both at the same time, retrieve the real slave interfaces
This needs to take in account both linux bridges and OVS bridges, since MAAS allows both of them to be configured.
2) retrieve the PCIe address of the daughter interface, can helpful to notice cross-physical card bonding
3) retrieve the NIC model
4) retrieve the current module and its version used by the interface
5) get the type of the link
  this includes also on checking sensitivity if use fiber optics

This can potentially be associated with the run-iperf action with a supplementary option to enable the output.

As a bonus, it may be useful to check the packet error counters to detect any physical issue on the real interfaces

James Page (james-page)
Changed in charm-magpie:
importance: Undecided → Wishlist
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.