MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty

Bug #1399016 reported by Narinder Gupta on 2014-12-03
294
This bug affects 5 people
Affects Status Importance Assigned to Milestone
MAAS
Undecided
Unassigned
maas (Ubuntu)
Critical
Andres Rodriguez
Precise
Critical
Marc Deslauriers
Trusty
Critical
Marc Deslauriers
Utopic
Critical
Marc Deslauriers
Vivid
Critical
Andres Rodriguez

Bug Description

Install trusty maas and upgrade the package libapache2-mod-wsgi to latest avilable with security fix MAAS UI stops responsing to any request.

ubuntu@upstream-maas-vm:~$ sudo apt-cache policy libapache2-mod-wsgi
libapache2-mod-wsgi:
  Installed: 3.4-4ubuntu2.1.14.04.1
  Candidate: 3.4-4ubuntu2.1.14.04.2
  Version table:
     3.4-4ubuntu2.1.14.04.2 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
 *** 3.4-4ubuntu2.1.14.04.1 0
        100 /var/lib/dpkg/status
     3.4-4ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
ubuntu@upstream-maas-vm:~$
ubuntu@upstream-maas-vm:~$
ubuntu@upstream-maas-vm:~$ sudo apt-get install libapache2-mod-wsgi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  libapache2-mod-wsgi
1 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
Need to get 67.4 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libapache2-mod-wsgi amd64 3.4-4ubuntu2.1.14.04.2 [67.4 kB]
Fetched 67.4 kB in 0s (1,954 kB/s)
(Reading database ... 107616 files and directories currently installed.)
Preparing to unpack .../libapache2-mod-wsgi_3.4-4ubuntu2.1.14.04.2_amd64.deb ...
Unpacking libapache2-mod-wsgi (3.4-4ubuntu2.1.14.04.2) over (3.4-4ubuntu2.1.14.04.1) ...
Setting up libapache2-mod-wsgi (3.4-4ubuntu2.1.14.04.2) ...
apache2_invoke wsgi: already enabled
 * Restarting web server apache2 [ OK ]
ubuntu@upstream-maas-vm:~$

http://172.16.16.14/MAAS does for timeout

maas.log
http://paste.ubuntu.com/9358984/
pserv.log
http://paste.ubuntu.com/9358991/

apache2 error.log
http://paste.ubuntu.com/9359010/

Related branches

CVE References

Narinder Gupta (narindergupta) wrote :

this patch CVE-2014-8583.patch is the issue cause in MAAS not to respond.

Marc Deslauriers (mdeslaur) wrote :

Looks like this is the problem:

[Sun Nov 30 06:55:11.818067 2014] [:alert] [pid 20247:tid 140076314253184] (2)No such file or directory: mod_wsgi (pid=20247): Unable to change working directory to '/home/maas'.

Raphaël Badin (rvb) wrote :

> [Sun Nov 30 06:55:11.818067 2014] [:alert] [pid 20247:tid 140076314253184] (2)No such file or directory: mod_wsgi (pid=20247): Unable to change working directory to '/home/maas'.

Indeed. This used to be not so much of a problem but with the new version is seems it became one. A workaround is to manually create /home/maas/.

Changed in maas (Ubuntu Precise):
status: New → Confirmed
Changed in maas (Ubuntu Trusty):
status: New → Confirmed
Changed in maas (Ubuntu Utopic):
status: New → Confirmed
Changed in maas (Ubuntu Vivid):
status: New → Confirmed
Changed in maas:
status: New → Confirmed
Marc Deslauriers (mdeslaur) wrote :

We are currently working on updated maas packages that will be published shortly to resolve this issue.

information type: Public → Public Security
Changed in maas (Ubuntu Precise):
importance: Undecided → Critical
Changed in maas (Ubuntu Trusty):
importance: Undecided → Critical
Changed in maas (Ubuntu Utopic):
importance: Undecided → Critical
Changed in maas (Ubuntu Vivid):
importance: Undecided → Critical
Changed in maas (Ubuntu Precise):
assignee: nobody → Marc Deslauriers (mdeslaur)
Changed in maas (Ubuntu Trusty):
assignee: nobody → Marc Deslauriers (mdeslaur)
Changed in maas (Ubuntu Utopic):
assignee: nobody → Marc Deslauriers (mdeslaur)
Changed in maas (Ubuntu Vivid):
assignee: nobody → Marc Deslauriers (mdeslaur)
assignee: Marc Deslauriers (mdeslaur) → nobody
assignee: nobody → Andres Rodriguez (andreserl)
tags: added: cts
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.7.0+bzr3299-0ubuntu2

---------------
maas (1.7.0+bzr3299-0ubuntu2) vivid; urgency=medium

  * debian/maas-common.postinst: Ensure that the maas user gets its home
    directory created in /var/lib/maas. (LP: #1399016)
 -- Andres Rodriguez <email address hidden> Thu, 04 Dec 2014 12:24:18 -0500

Changed in maas (Ubuntu Vivid):
status: Confirmed → Fix Released
Chris Johnston (cjohnston) wrote :

I have tried 1.7.0+bzr3299-0ubuntu2~trusty1 which works fine from a fresh install of maas but fails to fix the issue when upgrading maas.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.5.4+bzr2294-0ubuntu1.2

---------------
maas (1.5.4+bzr2294-0ubuntu1.2) trusty-security; urgency=medium

  * Fix compatibility with mod-wsgi security update (LP: #1399016)
    - debian/patches/home-directory.patch: specify a valid home directory
      for the maas user, since mod-wsgi no longer works without one.
 -- Marc Deslauriers <email address hidden> Thu, 04 Dec 2014 13:59:56 -0500

Changed in maas (Ubuntu Trusty):
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.7.0~beta8+bzr3272-0ubuntu1.2

---------------
maas (1.7.0~beta8+bzr3272-0ubuntu1.2) utopic-security; urgency=medium

  * Fix compatibility with mod-wsgi security update (LP: #1399016)
    - debian/patches/home-directory.patch: specify a valid home directory
      for the maas user, since mod-wsgi no longer works without one.
 -- Marc Deslauriers <email address hidden> Thu, 04 Dec 2014 13:59:15 -0500

Changed in maas (Ubuntu Utopic):
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.2+bzr1373+dfsg-0ubuntu1~12.04.6

---------------
maas (1.2+bzr1373+dfsg-0ubuntu1~12.04.6) precise-security; urgency=medium

  * Fix compatibility with mod-wsgi security update (LP: #1399016)
    - debian/patches/home-directory.patch: specify a valid home directory
      for the maas user, since mod-wsgi no longer works without one.
 -- Marc Deslauriers <email address hidden> Thu, 04 Dec 2014 14:00:28 -0500

Changed in maas (Ubuntu Precise):
status: Confirmed → Fix Released
Changed in maas:
status: Confirmed → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released

Hello Narinder, or anyone else affected,

Accepted maas into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/1.7.5+bzr3369-0ubuntu1~14.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Andres Rodriguez (andreserl) wrote :

This issue has been verified to work both on upgrade and fresh install, and has been QA'd. Marking verification-done.

tags: added: verification-done
removed: verification-needed
To post a comment you must log in.
This report contains Public Security information  Edit
Everyone can see this security related information.

Duplicates of this bug

Other bug subscribers