This bug was fixed in the package maas - 1.7.0~beta7+bzr3266-0ubuntu1 --------------- maas (1.7.0~beta7+bzr3266-0ubuntu1) utopic; urgency=medium
* New Upstream Snapshot, Beta 7 bzr3266 [ Jeroen Vermeulen ] * debian/extras/99-maas-sudoers debian/maas-dhcp.postinst debian/rules - Add second DHCP server instance for IPv6. * debian/maas-region-controller-min.install debian/maas-region-controller-min.lintian-overrides - Install deployment user-data: maas_configure_interfaces.py script. * debian/maas-cluster-controller.links debian/maas-cluster-controller.install debian/maas-cluster-controller.postinst - Reflect Celery removal changes made in trunk r3067. - Don't install celeryconfig_cluster.py any longer. - Don't install maas_local_celeryconfig_cluster.py any longer. - Don't symlink maas_local_celeryconfig_cluster.py from /etc to /usr. - Don't insert UUID into maas_local_celeryconfig_cluster.py. [ Andres Rodriguez ] * debian/maas-region-controller-min.postrm: Cleanup lefover files. * debian/maas-dhcp.postrm: Clean leftover configs. * Provide new maas-proxy package that replaces the usage of squid-deb-proxy: - debian/control: New maas-proxy package that replaces the usage of squid-deb-proxy; Drop depends on squid-deb-proxy. - Add upstrart job. - Ensure squid3 is stopped as maas-proxy uses a caching proxy. * Remove Celery references to cluster controller: - Rename upstart job from maas-pserv to maas-cluster; rename maas-cluster-celery to maas-cluster-register. Ensure services are stopped on upgrade. - debian/maintscript: Cleanup config files. - Remove all references to the MAAS celery daemon and config files as we don't use it like that anymore * Move some entries in debian/maintscript to debian/maas-cluster-controller.maintscript * Remove usage of txlongpoll and rabbitmq-server. Handle upgrades to ensure these are removed correctly. [ Jason Hobbs ] * debian/maas-region-controller-min.install: Install maas-generate-winrm-cert script. [ Raphaƫl Badin ] * debian/extras/maas-region-admin: Bypass django-admin as it prints spurious messages to stdout (LP: #1365130). [Louis Bouchard] * debian/maas-cluster-controller.postinst: - Exclude /var/log/maas/rsyslog when changing ownership (LP: #1346703) [Gavin Panella] * debian/maas-cluster-controller.maas-clusterd.upstart: - Don't start-up the cluster controller unless a shared-secret has been installed. * debian/maas-cluster-controller.maas-cluster-register.upstart: Drop. -- Andres Rodriguez <andres...@ubuntu.com> Thu, 21 Aug 2014 19:36:30 -0400 ** Changed in: maas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1346703 Title: /var/log/maas/rsyslog has incorrect permission To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346703/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs