Error "Cannot find OS information - Reason: (Cannot load Libosinfo: (No module named gi.repository.Libosinfo))" - spamming n-cpu logs

[Matt Riedemann]

http://logs.openstack.org/12/276812/2/check/gate-manila-tempest-dsvm-neutron/1b42ac2/logs/screen-n-cpu.txt.gz?level=TRACE

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Cannot%20find%20OS%20information%20-%20Reason%3A%20(Cannot%20load%20Libosinfo%3A%20(No%20module%20named%20gi.repository.Libosinfo))%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d

Looks like it started spiking around 2/6 for some reason.

[Matt Riedemann (mriedem)]

These were merged on 2/6 to use this code:

https://github.com/openstack/nova/commit/9de8f7230d069e4da9736f09ad5d17773315b476

https://github.com/openstack/nova/commit/5f5590f7f4c90fcd1869dadc6ec7e5ea5ab6979e

That's why it started showing up then.

[Matt Riedemann (mriedem)]

According to the spec:

http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/libvirt-hardware-policy-from-libosinfo.html#other-deployer-impact

libosinfo should be installed, but if it's not, things should still continue to work as they did before. I'm not sure if that's happening or not because I'm not sure if what we're using in the gate testing would rely on this code.