usually when there is an issue with non found modules it's better to go back to vdsm top dir and make clean ./autogen.sh make then try again Also make sure you are running against the correct tested python version, i.e. trying to run tox -e storage-py36 on fc30 with py37 would also fail for non-found modules. On Sun, Nov 24, 2019 at 11:10 AM Eyal Shenitzky <eshenitz(a)redhat.com&gt; wrote: > Hi, > > I am failing to run VDSM tests locally using tox, failed with the > following error: > > ImportError while loading conftest > '/home/eshenitz/git/vdsm/tests/storage/conftest.py'. > storage/conftest.py:36: in <module> > from vdsm import jobs > ../lib/vdsm/jobs.py:29: in <module> > from vdsm.config import config > ../lib/vdsm/config.py:29: in <module> > from vdsm.common.config import * # NOQA: F401, F403 > E ModuleNotFoundError: No module named 'vdsm.common.config' > > Did someone encounter this problem? > I cannot run vdsm-tool configure --force because it exists only in > python-2 version > > -- > Regards, > Eyal Shenitzky > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/J5BDM6CSMZI... >