I just upgraded from 14.04 all the way to 15.10.
2015-10-28 10:17:17 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~14.04.1
1.7.6+bzr3376-0ubuntu2~15.04.1
2015-10-28 10:54:59 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~15.04.1
1.8.3+bzr4053-0ubuntu1
MAAS wouldn't start up, with this in syslo
[Expired for maas (Ubuntu) because there has been no activity for 60
days.]
** Changed in: maas (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360400
Tit
On Tuesday 26 August 2014 01:28:05 you wrote:
> I Installed 1.6.0 and upgraded to 1.7.0~beta1. This was reproduced more
> than twice so i think we can reproduce to figure out what;s wrong.
I know what's wrong without looking I think:
You didn't accept the changes in the packaging for maas_local_s
Julian,
I did have maas-django.log. The old owners of the maas.log there were
maas:maas but the new ones (after upgrade) syslog:syslog.
I Installed 1.6.0 and upgraded to 1.7.0~beta1. This was reproduced more
than twice so i think we can reproduce to figure out what;s wrong.
On Mon, Aug 25, 2014
The permissions for maas.log should *not* be maas:maas. There is a line
in the packaging that does:
chown syslog:syslog /var/log/maas/maas.log
which is correct, because the only process that writes maas.log is
syslog.
Questions:
* what were the old owners of the maas.log?
* did you ha
Packaging bug.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: Triaged => Invalid
** Changed in: maas
Milestone: 1.7.0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
