← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1584040] Re: Horizon wsgi can run in the wrong WSGIProcessGroup

 

This bug was fixed in the package horizon - 2:10.0.0~b1-0ubuntu2~cloud0
---------------

 horizon (2:10.0.0~b1-0ubuntu2~cloud0) xenial-newton; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 horizon (2:10.0.0~b1-0ubuntu2) yakkety; urgency=medium
 .
   * Fold Ubuntu theme into themes installed as part of the core
     openstack-dashboard package:
     - d/openstack-dashboard-ubuntu-theme.*,control:
       Make openstack-dashboard-ubuntu-theme transitional.
     - d/openstack-dashboard.install: Install Ubuntu theme.
     - d/theme/ubuntu_theme.py: Drop, no longer needed.
     - d/p/ubuntu_settings.patch: Add Ubuntu theme to list of available
       themes for users.
   * d/p/*: Refresh.
   * d/openstack-dashboard.conf: Ensure wsgi process-group is set for
     horizon application (LP: #1584040), set process display-name to
     wsgi application group for ease of debugging.


** Changed in: cloud-archive
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1584040

Title:
  Horizon wsgi can run in the wrong WSGIProcessGroup

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive icehouse series:
  New
Status in Ubuntu Cloud Archive kilo series:
  New
Status in Ubuntu Cloud Archive liberty series:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Trusty:
  New
Status in horizon source package in Wily:
  New
Status in horizon source package in Xenial:
  New
Status in horizon source package in Yakkety:
  Fix Released

Bug description:
  Horizon wsgi can run in the wrong WSGIProcessGroup when multiple
  WSGIProcessGroup are defined. Typically with the 2 following
  configurations enabled on apache2:

  # /etc/apache2/conf-enabled/openstack-dashboard.conf
     WSGIScriptAlias /horizon /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi
     WSGIDaemonProcess horizon user=horizon group=horizon processes=3 threads=10
     WSGIProcessGroup horizon
     Alias /static /usr/share/openstack-dashboard/openstack_dashboard/static/
     Alias /horizon/static /usr/share/openstack-dashboard/openstack_dashboard/static/
     <Directory /usr/share/openstack-dashboard/openstack_dashboard/wsgi>
       Order allow,deny
       Allow from all
     </Directory>

  # /etc/apache2/conf-enabled/wsgi.conf
     WSGIScriptAlias /mywsgi /usr/share/mywsgi/.. process-group=mywsgi
     WSGIDaemonProcess mywsgi user=mywsgi group=mywsgi processes=5 threads=10
     WSGIProcessGroup mywsgi
     <Directory /usr/share/mywsgi>
       Order allow,deny
       Allow from all
     </Directory>

  Nothing ensures that Horizon wsgi will run in "horizon"
  WSGIProcessGroup.

  
  To ensure it we should use:
     WSGIScriptAlias /horizon /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi processes-group=horizon
  instead of:
     WSGIScriptAlias /horizon /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi

  
  It affects my Kilo openstack-dashboard on Trusty BUT should affect every openstack-dashboard on every ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1584040/+subscriptions