Runtime error: invalid memory address or nil pointer dereference
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Committed
|
Critical
|
Heather Lanigan | ||
3.4 |
Fix Released
|
Critical
|
Heather Lanigan | ||
3.5 |
Fix Committed
|
Critical
|
Heather Lanigan |
Bug Description
Juju version: 3.4.2
Juju manual cloud
Have seen a couple of similar errors, but looks like this one is new. I get a "invalid memory address or nil pointer dereference" in juju when trying to deploy a charmed app (Landscape) to a pre-created container on a manual cloud.
This is a manual cloud, with 3 pre-created VMs inside. Each VM has 3 containers attached to it. All are in status "started" with an IP assigned.
Traceback from the juju deploy command (with --verbose): https:/
command looks like:
```
juju deploy landscape-server --channel stable --revision 107 --to 0/lxd/0 --debug
```
```
Happy to provide more logs, but even with verbose there's not a ton of details.
Issue is reproducible on this setup (eg. every deploy attempt results in the error) but haven't destroyed the env to see if it continues to occur.
Changed in juju: | |
status: | Incomplete → Triaged |
importance: | Undecided → Critical |
assignee: | nobody → Heather Lanigan (hmlanigan) |
milestone: | none → 3.3.5 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 3.3.5 → 3.3.6 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Can you check the log in /var/log/ juju/machine- x.log? This should have the stack trace. What you see in the pastebin is just the client side reporting of the error.