i've done some looking into this as well. As correctly indentified, the issue is with the import_modules_from_package function in osprofiler._utils.
The main difference between how TripleO configures horizon and how devstack configures horizon is that in TripleO, horizon is installed in a python virtualenv along with it's dependencies. The following line in the django.wsgi file for Horizon adds a relative path to sys.path:
i've done some looking into this as well. As correctly indentified, the issue is with the import_ modules_ from_package function in osprofiler._utils.
The main difference between how TripleO configures horizon and how devstack configures horizon is that in TripleO, horizon is installed in a python virtualenv along with it's dependencies. The following line in the django.wsgi file for Horizon adds a relative path to sys.path:
sys.path.insert(0, os.path. join(os. path.dirname( os.path. realpath( __file_ _)), '../..'))
osprofiler ends up getting imported from the venv using that relative path (with a "../..") in it, and thus triggering this bug.