[Bug 1492088] Re: juju bootstrap fails inside a wily container
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492088 Title: juju bootstrap fails inside a wily container To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1492088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492088] Re: juju bootstrap fails inside a wily container
** Changed in: juju-core Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492088 Title: juju bootstrap fails inside a wily container To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1492088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492088] Re: juju bootstrap fails inside a wily container
Juju will issue a systemctl link to link the unit files, then run systemctl enable. I cannot recreate this issue on wily, either as a host, or a wily container running on a wily host (with or without KVM enabled). Martin - what information could Adam gather to help debug the issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492088 Title: juju bootstrap fails inside a wily container To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1492088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492088] Re: juju bootstrap fails inside a wily container
2015-09-22 22:28:47 ERROR juju.service.systemd service.go:145 dbus
enable request failed for service "juju-db-ubuntu-local": Unit name
/var/lib/juju/init/juju-db-ubuntu-local/juju-db-ubuntu-local.service is
not valid.
What is juju trying to do here? Indeed this isn't an unit *name*, it's a
path to a unit. But you can't have units in arbitrary paths, they need
to be in {/etc,/lib,/run}/systemd/system/. They can be symlinked there
with "systemctl link" or plain ln -s.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492088
Title:
juju bootstrap fails inside a wily container
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1492088/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492088] Re: juju bootstrap fails inside a wily container
Opening up a systemd record so that team can take a look. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492088 Title: juju bootstrap fails inside a wily container To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1492088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
