** No longer affects: juju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536522
Title:
juju-local: systemd units fail on boot if /home is not accessible
before logging in
To manage notifications
This does not affect juju-2.0, only 1.0. With 2.0 there is no cluttering
of the host any more but everything is put into the controller LXD
container.
** Package changed: juju-core (Ubuntu) => juju-core-1 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Also affects: juju
Importance: Undecided
Status: New
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => High
** Changed in: juju
Milestone: None => 2.0-beta18
--
You received this bug notification because you are a member of Ubunt
Oh, I see what's wrong: They run /var/lib/juju/init/juju-agent-martin-
local/exec-start.sh, which runs
/home/martin/.juju/local/tools/machine-0/jujud
This can't work, as my home directory does not exist until I log in
(it's encrypted). This will equally affect /home on NFS and the like.
* Do
