Workaround horizon fails when osprofiler installed

There is a very long and boring story. This bug was reported 2 years ago,
moved to in progress and seems like never fixed. Due to the very interesting
way how everything is working it's not so often reproducible. In our case,
it's really failing. So, we shouldn't have osprofiler installed with Horizon
now, but new version of python-mistralclient that horizon depends on introduced
osprofiler as direct dependency and so horizon started failing. This workaround
doesn't disable or break osprofiler, it's just making very safe (and duty, yes)
change to make it working in any case.

Change-Id: If3e30e065169c1b1a1514dc67b887be294e6fb54
This commit is contained in:
Sergey Lukjanov 2016-08-29 23:06:24 -07:00
parent fa94640e15
commit 56a7c6f797
1 changed files with 3 additions and 0 deletions

View File

@ -20,6 +20,9 @@ RUN mkdir -p /etc/openstack-dashboard /home/horizon /var/www/cgi-bin/horizon \
ENV PATH /var/lib/venv/bin:$PATH
# Workaround for https://bugs.launchpad.net/osprofiler/+bug/1361235
RUN sed -i "s#'../..'#os.path.realpath('../..')#" /var/lib/microservices/venv/lib/python2.7/site-packages/openstack_dashboard/wsgi/django.wsgi
COPY daemon.sh /usr/local/bin/daemon.sh
COPY horizon_sudoers /etc/sudoers.d/horizon_sudoers
RUN chmod 755 /usr/local/bin/daemon.sh \