** Changed in: juju
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637230
Title:
[2.0] Error calling 'lxd forkstart
To manage notifications about this bug go
** Changed in: lxd (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/1637230
Title:
[2.0] Error calling 'lxd forkstart
To manage notifications about this b
@Larry,
2.1-rc2 might not be the best release to recreate this - either 2.1.2 or
2.2-alpha1 or daily snaps would be best. Could you please re-try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637230
I have tried to recreate however I am now seeing the agent not coming up
on the unit and can't ssh it it (connection refused):
jenkins@juju-a6a70b-integration-juju2-1:~$ juju status 5 --format=yaml
model:
name: ci-oil-slave14
controller: maas
cloud: maas
version: 2.1-rc2
machines:
"5":
** Changed in: juju
Milestone: 2.1-rc1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637230
Title:
[2.0] Error calling 'lxd forkstart
To manage notifications about this bug go to:
http
We suspect this is more LXD related than Juju.
Marking the bug as Incomplete for Juju until Stephane's and Tycho's questions
are answered.
** Changed in: juju
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The log above suggests that the containers failed in the pre-start hook.
Any error message would therefore be found in /var/log/lxd/lxd.log
rather than in the container log.
Can you attach "lxc info" for this system so we can know its liblxc
version, lxd version, kernel version and storage configu
