sos 3.2 has been released Tue Sep 30 2014. Using sos 3.2 for collecting vdsm data it fails with the following error: # sosreport -o vdsm sosreport (version 3.2) plugin vdsm does not install, skipping: No module named config a non-existing plugin (vdsm) was specified in the command line [root@mididell ~]# sosreport -o vdsm --verbose sosreport (version 3.2) plugin vdsm does not install, skipping: No module named config a non-existing plugin (vdsm) was specified in the command line # sosreport -o vdsm --debug sosreport (version 3.2) plugin vdsm does not install, skipping: No module named config Traceback (most recent call last): File "/usr/sbin/sosreport", line 25, in <module> main(sys.argv[1:]) File "/usr/lib/python2.7/site-packages/sos/sosreport.py", line 1411, in main sos.execute() ImportError: No module named config > /usr/lib/python2.7/site-packages/sos/plugins/vdsm.py(39)_importVdsmPylibModule() -> modName, [os.path.join(get_python_lib(True), "vdsm")]) side note: pep8 /usr/lib/python2.7/site-packages/sos/plugins/vdsm.py /usr/lib/python2.7/site-packages/sos/plugins/vdsm.py:130:80: E501 line too long (83 > 79 characters) vdsm-4.16.7-39.gitd88aba8.fc20.x86_64
Verified on CentOS 6.6, it doesn't work on sos 2.2 too. # sosreport --diagnose --verbose -o vdsm sosreport (version 2.2) plugin vdsm.py does not install, skipping no valid plugins were enabled
After further investigation, looks like vdsm sos plugin is trying to load a config python module from /usr/lib64/python2.6/site-packages/vdsm being on a x86_64 system, but fails since that direcotry doesn't exist and the config module is in /usr/lib/python2.6/site-packages/vdsm
just a note for the test case: functional test exist: - install vdsm-tests.rpm - get vdsm to run - go to /usr/share/vdsm/tests - execute ./run_tests.sh functional/sosPluginTests.py
This is an automated message: This bug should be fixed in oVirt 3.5.1 RC1, moving to QA
oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.