The original bug (before the comment #6) was caused by the fact that rethtool doesn't work with 'virtio' interfaces. In that case it fails to execute 'ioctl' method [0] and that leads to empty value passed to lspci.
From the original log [1] it can be seen that ruby constantly tries to execute lspci with wrong (empty) parameter, and does this *before* a segfault occurs. That means that segfaul is not a root cause, and even hardly can be an issue because to reproduce it one have to run it hundreds of times. As I said, the *real* root cause here is virtio network interface that isn't supported.
If anyone think that segfault is important please file a separate bug for this.
I'm passing the bug back because in any way we can't use virtio network interfaces on slave nodes and thus this bug have no real sense.
The original bug (before the comment #6) was caused by the fact that rethtool doesn't work with 'virtio' interfaces. In that case it fails to execute 'ioctl' method [0] and that leads to empty value passed to lspci.
From the original log [1] it can be seen that ruby constantly tries to execute lspci with wrong (empty) parameter, and does this *before* a segfault occurs. That means that segfaul is not a root cause, and even hardly can be an issue because to reproduce it one have to run it hundreds of times. As I said, the *real* root cause here is virtio network interface that isn't supported.
If anyone think that segfault is important please file a separate bug for this.
I'm passing the bug back because in any way we can't use virtio network interfaces on slave nodes and thus this bug have no real sense.
[0] https:/ /review. fuel-infra. org/gitweb? p=packages/ trusty/ rethtool. git;a=blob; f=debian/ patches/ 0001-Added- interface- driver- and-bus_ info-support. patch;h= 41abd6b0b88439a 29f29fad96a6ab3 b2a09ffad3; hb=refs/ heads/master# l61 /goo.gl/ F7hJtw
[1] https:/