[Bug 1346703] Re: /var/log/maas/rsyslog has incorrect permission

Wed Oct 22 03:20:00 UTC 2014

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 <andreserl at 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
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1346703

Title:
  /var/log/maas/rsyslog has incorrect permission

Status in “maas” package in Ubuntu:
  Fix Released
Status in “maas” source package in Trusty:
  In Progress

Bug description:
  [SRU justification]
  This fix is required to allow maas to log rsyslog events

  [Impact]
  Without this fix, no d-i log from MAAS can be written

  [Fix]
  Change the post install script code that sets permissions in /var/log/maas
  directory

  [Test Case]

  1. create pristine Ubuntu 14.04 LTS box 
  2. sudo apt-get update && sudo apt-get install maas 

  Actual result: 
  /var/log/maas/rsyslog/ is owned by maas:maas and not writable by syslog user. No log will be written. 
  $ ll /var/log/maas/rsyslog/ 
  drwxr-xr-x 2 maas maas 4096 Jul 16 06:26 ./ 

  Expected result: 
  /var/log/maas/rsyslog/ is writable by syslog user to store d-i log from MAAS nodes. 

  [Regression]
  None expected as only the rsyslog ownership is changed explicitely

  [Description of the problem]

  /var/log/maas/rsyslog/ is owned by maas:maas and has 755 permission
  after maas package installation. Therefore rsyslogd cannot write logs
  into the directory.

  How to reproduce:
   1. prepare pristine trusty box
   2. sudo apt-get install maas

  Expected result:
  /var/log/maas/rsyslog/ is owned by for example syslog:syslog.

  Actual result:
  $ ll /var/log/maas/rsyslog/
  drwxr-xr-x 2 maas maas 4096 Jul 22 01:13 ./

  Workaround:

  $ sudo chown -R syslog:syslog /var/log/maas/rsyslog

  It seems that 3 packages are trying to set owner related /var/log/maas/*.
  ====
  $ grep -r chown.*/var/log/maas /var/lib/dpkg/info/
  /var/lib/dpkg/info/maas-cluster-controller.postinst:    chown -R maas:maas /var/log/maas
  /var/lib/dpkg/info/maas-region-controller-min.postinst:    chown -R maas:maas /var/log/maas
  /var/lib/dpkg/info/maas-region-controller-min.postinst:    chown -R syslog:syslog /var/log/maas/rsyslog
  /var/lib/dpkg/info/maas-region-controller.postinst:     chown -R maas:maas /var/log/maas
  /var/lib/dpkg/info/maas-region-controller.postinst:     chown -R syslog:syslog /var/log/maas/rsyslog
  ====

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: maas 1.5.2+bzr2282-0ubuntu0.2
  ProcVersionSignature: User Name 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Tue Jul 22 01:15:20 2014
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: maas
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346703/+subscriptions