[nailgun-agent] Platform bus ethernet devices can't be described by lspci

[Alexandru Avadanii]

This was observed on AArch64 hardware, where ethernet devices may be located on the platform bus (see [1], [2]), and not on standard PCI tree, like nailgun-agent expects them.

Steps to reproduce:
1. Deploy Fuel, bootstrap nodes with platform bus ethernet (e.g. APM Mustang)
2. Analyze nailgun-agent logs

Expected results:
Slot information is correctly extracted by nailgun-agent from lspci output, using a call like `lspci -vvv -s SLOT_NO`.

Actual results:
Slot information cannot be found, since the detected SLOT_NO is invalid in lspci context:

e.g. for APM boards:
- SLOT_NO is "17020000.ethernet"
- nailgun-agent logs: "W, [2016-07-12T19:33:24.589605 #27313] WARN -- : Can't get data from lspci. Reason: lspci exited with status 1"
- lspci raw output:

root@node-1:~# lspci -vvv -s 17020000.ethernet
lspci: -s: Invalid slot number

Description of the environment:
 Operation system: Ubuntu Trusty 14.04 (arm64)
 Versions of components: stable/mitaka
 Related projects installed: Fuel@OPNFV

[1] https://www.kernel.org/doc/Documentation/driver-model/platform.txt
[2] http://electronics.stackexchange.com/questions/110713/what-is-platform-bus-in-embedded-systems

[Dmitry Pyzhov (dpyzhov)]

mos-linux team, could you suggest a solution for this hardware?

[Dmitry Teselkin (teselkin-d)]

We can investigate this, but since we're not supporting arm64 moving the bug to 'low' priority.

[Albert Syriy (asyriy)]

Move forward due to low priority