server suite needs more network device info in results

[Jeff Lane ]

Several times now I've run into situations where one or more network devices failed. This is usually because of misconfiguration or some other similar issue.

It would be really useful to have ifconfig and possibly ethtool info in the output for failures.

[Daniel Manrique (roadmr)]

We have ethernet/ethtool_info, it's a local job that builds ethernet/ethertool_check_.* jobs for each interface.

Is that enough, and could we add e.g. ethernet/ifconfig_info (or maybe something more generic like network_info) to dump ifconfig, route and whatnot?

Are you happy with the multiple-job (local-job) mechanism, or would a single humongous collect-all-interfaces script be better?

We can definitely add this to the network script itself. However, if it doesn't change the network configurations itself, then the config is static and we should be able to query it at any point.

To contrast, I recently added some changes to the wireless tests to output iw dev link information during testing. This had to be injected in the middle of the job's command because the test does create the connection dynamically, then destroys it after the testing is finished.

Let me know your thoughts on this.

[Jeff Lane  (bladernr)]

Grrr... I need to remember to start just automatically assigning these things to myself... heh

So I just spend a couple hours learning a bit about sockets in python and modified network_device_info to do essentially the same thing that network_info does now.

So now I've deleted that branch and will resolve this simply by adding the ethertool jobs and the network_info job to the server whitelists... that should be enough for now.