maas 1.7beta5 crash during package install

[James Troup]

I just tried to install maas 1.7beta5 into a fresh(ish) trusty install and it failed with what looks like a race. When I ran dpkg --configure --pending, the install succeeded.

[Christian Reis (kiko)]

Here's a snippet of the error:

Module wsgi already enabled
chown: changing ownership of ‘/var/log/maas/oops/2014-10-09/OOPS-9614efa03f95a2c5dee492b1a0a4372b.tmp’: No such file or directory
dpkg: error processing package maas-region-controller-min (--configure):

Am I reading that right -- why is an OOPS getting generated upon installation?

[James Troup (elmo)]

Over 10,000 OOPS were generated during install. I no longer have them, but the bulk were to do with permissions on /var/log/maas/. I can't reproduce the problem again although I can see exactly how the race occurred given the number of OOPSes. When I said fresh(ish), I was simplifying. This box was re-purposed, had MAAS 1.5 installed on it, upgraded to trusty and then I purged MAAS 1.5 and installed MAAS 1.7beta5 in an attempt to get a "fresh" start.

If no one else can reproduce the crash and if we have good testing of our upgrade path from 1.5 to 1.7, feel free to disregard this bug as I can't really vouch for the state of the box (a lot of people have root on it).

[Julian Edwards (julian-edwards)]

I just installed 1.7.0~beta5+bzr3198-0ubuntu1 on a fresh trusty canonistack instance and it looked ok.

I'll invalidate this bug on that basis and your comment above, but please re-open if you see it happen again.