Hi Adriene, thanks for reporting this issue!
Even though this is a "system" file, it is controlled by files in user
home directories (~/.juju/environments.yaml) and so I don't think we can
purge the upstart jobs.
I do think we can add a check to the upstart job's pre-start for juju,
and if it is not installed, we can not start the job.
This is probably a duplicate of bug #1006553 , which is also caused by
starting these things at reboot, even though the rest of the things they
are there to serve (zookeeper and the lxc containers themselves) are not
autostarted.
Marking as Triaged, opening upstream task, and setting importance to
Low, since this is just "annoying", not really causing any adverse
effect.
** Changed in: juju (Ubuntu)
Status: New => Triaged
** Changed in: juju (Ubuntu)
Importance: Undecided => Low
** Also affects: juju
Importance: Undecided
Status: New
** Changed in: juju
Status: New => Confirmed
** Changed in: juju
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013457
Title:
twistd still autostarted for juju after juju is removed from system
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1013457/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
