Canonical Juju

"lxd-provisioner": panic resulted in: runtime error: invalid memory address or nil pointer dereference

Bug #1728066 reported by Jason Hobbs on 2017-10-27

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical Juju	Fix Released	Critical	Heather Lanigan	Canonical Juju 2.3-beta2

Bug Description

Starting with juju_2.3-beta2+develop-9456701 and lxd 2.0.10, containers aren't starting up on machines:

http://paste.ubuntu.com/25830665/

In the log I see errors like this:
machine-0: 14:33:29 INFO juju.worker stopped "lxd-provisioner", err: panic resulted in: runtime error: invalid memory address or nil pointer dereference

There are no containers on any of the machines.

I attached logs from a failure.

Tags:

Revision history for this message

Jason Hobbs (jason-hobbs) wrote on 2017-10-27:

juju-crashdump-82181013-550e-4b1f-9667-e07ba23aae24.tar.xz Edit (4.8 MiB, application/x-tar)

Revision history for this message

Heather Lanigan (hmlanigan) wrote on 2017-10-27:

caused by https://github.com/juju/juju/pull/7838

Can be easily reproduced by:
1. juju bootstrap localhost
2. juju add-machine
3. juju deploy mysql --to lxd:0

Changed in juju:
assignee:	nobody → Heather Lanigan (hmlanigan)
importance:	Undecided → High
status:	New → Triaged

Revision history for this message

Heather Lanigan (hmlanigan) wrote on 2017-10-27:

NewContainerProvisioner() didn't have a DistributionGroupFinder for the provisioner, so we panic'd in provisioner_task.startMachines() trying to use it.