Created attachment 1726425 [details] traceback Description of problem: When building and installing the oVirt DWH development environment according to the doc https://ovirt.org/develop/dwh-development-environment.html, starting the dwh service failed. The problem seems to be caused by this line in packaging/services/ovirt-engine-dwhd/config.py: DEV_PYTHON_DIR = '.../ovirt-engine/usr/lib/python2.7/site-packages' But the ovirt-engine now doesn't use/install to python2.7 and the .../ovirt-engine/usr/lib/python2.7 doesn't exist. This happens because python3 is used by default. Than the DWH startup script cannot find required packages. Version-Release number of selected component (if applicable): DWH: latest version, commit e62bd32f52b063def71ba898f1d9da379d5bac7f DHW installed on Fedora 31 How reproducible: always Steps to Reproduce: 1. Build and install the ovirt-engine dev environment 2. Follow the doc "oVirt DWH development environment": https://ovirt.org/develop/dwh-development-environment.html 3. Start the DWH service: $ $HOME/ovirt-engine/share/ovirt-engine-dwh/services/ovirt-engine-dwhd/ovirt-engine-dwhd.py start Actual results: The DWH service didn't start and raised ModuleNotFoundError. Expected results: The DWH service starts successfully. Additional info: Although this problem is related to the development environment, python 2 is obsolete and the DWH shouldn't use it anymore.
Can you please check if change 112095 works for you, and mark verified? Thanks!
Hello Yedidyah, yes, the change 112095 works for me, it fixes the problem with starting the DWH service. Also I can see "DEV_PYTHON_DIR = '.../ovirt-engine/usr/lib/python3.7/site-packages'" and not "...python2.7..." in packaging/services/ovirt-engine-dwhd/config.py after the dwh installation. However there are some improvements that can be done as already mentioned in gerrit. Thank you very much!
This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE. If you believe special care is required, feel free to re-open to ON_QA status.