I noticed that /var/log/maas was owned by root.root. Chowning that directory to maas.maas and restarting maas-rackd enabled the rackd.log to get written. Looks like this bug is really about having the packaging ensure the permissions of /var/log/maas are appropriate.
I noticed that /var/log/maas was owned by root.root. Chowning that directory to maas.maas and restarting maas-rackd enabled the rackd.log to get written. Looks like this bug is really about having the packaging ensure the permissions of /var/log/maas are appropriate.