juju deploy existing charm after upgrading gives nil pointer panic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Simon Richardson |
Bug Description
If I try to deploy a charm that already exists in the DB after upgrading from juju 2.4.7 to 2.5-beta3, I get a nil pointer error because the charm's LXDProfile is nil in the database. We need an upgrade step to add the field to existing charms so that calling Charms.CharmInfo works correctly for them. This probably needs to happen when the controller upgrades, rather than waiting for the model to be upgraded.
machine-0: 17:54:00 CRITICAL juju.rpc panic running request {MethodCaller:
nvalid memory address or nil pointer dereference
goroutine 414796 [running]:
runtime/
github.
panic(0x3070e20, 0x654f2d0)
github.
github.
reflect.
reflect.
github.
github.
github.
created by github.
So, for example:
// In 2.4.7 controller
juju deploy ~jameinel/
juju upgrade-juju -m controller --agent-version 2.5-beta3
juju deploy ~/jameinel/
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Critical |
assignee: | nobody → Heather Lanigan (hmlanigan) |
Changed in juju: | |
assignee: | Heather Lanigan (hmlanigan) → Simon Richardson (simonrichardson) |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |