*** This bug is a duplicate of bug 1631254 ***
https://bugs.launchpad.net/bugs/1631254
** This bug has been marked a duplicate of bug 1631254
[2.0rc3] lxd containers do not autostart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
In my setup I have 14 containers in a control node, after shutdown and start
the node, some of them started but others still down.
I use juju 2.0.2
xenial 16.04.1
root@C1N4-controller:~# lxc list
+--+-++--++---+
machine 1 log
** Attachment added: "machine-1.log"
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1640079/+attachment/4805494/+files/machine-1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: juju
Milestone: 2.1-beta4 => 2.1-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to:
** Changed in: juju
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to
The team is actively looking at the keys for the config in lp:1631254.
We'll verify that this is indeed the same issue but we're looking to
have this fix in for 2.1 final and should be ready for 2.1 RC1 after the
holiday break.
--
You received this bug notification because you are a member of Ubu
So, LXD will try to restore containers to whatever state they were in,
even if boot.autostart isn't set to true. So that may be what's making
this work despite the wrong key being set (user.boot.autostart vs
boot.autostart).
In any case, LXD completely ignores all user.* keys as those are for
user
Just one datapoint.
I have a 100+ LXDs over here and they all autostart when host is
rebooted. These are on different juju versions (beta15 and 2.0.1) and
they all have:
user.boot.autostart: "true"
I repeat, they autostart every time. Difference is that this is Ubuntu
14.04 and LXD 2.0.3 and 2
** Changed in: juju
Milestone: None => 2.1-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to:
https
** Changed in: juju
Milestone: 2.1-beta2 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to:
htt
** Changed in: juju
Milestone: 2.1-beta1 => 2.1-beta2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to
** Changed in: juju
Assignee: (unassigned) => Richard Harding (rharding)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications
Re-targeting to "juju" launchpad project which tracks Juju 2.x issues.
** Also affects: juju
Importance: Undecided
Status: New
** No longer affects: juju-core
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => High
** Changed in: juju
** Tags added: lxd-provider openstack uosci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to:
https://bugs
** Also affects: juju-core
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/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about t
Thanks Stephane.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
juju version 2.0.0
http://paste.ubuntu.com/23446533/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to:
htt
Confirmed that there is a Juju bug where all LXD keys are prefixed with
"user.", so using "user.boot.autostart" and "user.user.juju-model"
rather than "boot.autostart" and "user.juju-model".
So LXD is most likely fine, if the right keys are set :)
** Package changed: lxd (Ubuntu) => juju (Ubuntu)
So the problem is that your containers have "user.boot.autostart"
instead of "boot.autostart", that's why LXD doesn't do anything about
it.
That may well be a Juju bug. Can you tell us what version of Juju you're
using exactly?
--
You received this bug notification because you are a member of Ub
$ cat /var/log/lxd/lxd.log
http://paste.ubuntu.com/23446347/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go
Interesting, ok, so with that setup, LXD should absolutely have
attempted to bring those containers online.
My best guess is that those network bridges or something related to them
didn't exist at the time LXD was started during boot, it then attempted
to boot all your containers which failed, exp
I have 3 nodes (3 OpenStack controllers) where there are multiple lxds.
All the LXDs are managed by Juju.
-> lxc list
http://paste.ubuntu.com/23446124/
-> lxc info
http://paste.ubuntu.com/23446131/
-> lxc config show juju-e25772-0-lxd-8
http://paste.ubuntu.com/23446138/
I'm not m
We'd need to see a:
- lxc list
- lxc info
- lxc config show
When this bug happens, after a reboot, to see what's going on.
LXD is supposed to record the state of all containers on shutdown and restore
them to their last state after reboot, so this suggests that containers were
somehow shut
23 matches
Mail list logo
