LXD container inside LXD machine stuck in "pending"

Bug #1994907 reported by Jordan Barrett
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Unassigned

Bug Description

Deploy a bionic charm on LXD:
    juju deploy tiny-bash --to lxd --series bionic
This will start a new bionic machine and a bionic LXD container inside this machine. The bionic machine starts correctly, and the container seems to start, but the container's state is never set to "started". It gets stuck in this state:
----------------------------------------------------------------
Machine State Address Inst id Series AZ Message
0 started 10.120.49.53 juju-1bf0b8-0 bionic Running
0/lxd/0 pending juju-1bf0b8-0-lxd-0 bionic Container started
----------------------------------------------------------------

This is on
- Juju 2.9.37-ubuntu-amd64-1650771
- LXD 5.7-749a602
- Ubuntu 20.04.5 LTS

LXD version inside the machine is 3.0.3.

Changed in juju:
milestone: none → 2.9.37
importance: Undecided → High
status: New → Triaged
Revision history for this message
Jordan Barrett (barrettj12) wrote :

Just observed the same thing with a focal LXD container inside a focal machine. Inside this machine, the LXD version is 5.7-749a602.

summary: - bionic lxd container in bionic machine stuck in "pending"
+ LXD container inside LXD machine stuck in "pending"
Revision history for this message
Jordan Barrett (barrettj12) wrote :

And observed the same with jammy inside jammy. Clearly this is a far reaching issue.

Changed in juju:
milestone: 2.9.37 → 2.9.38
Changed in juju:
milestone: 2.9.38 → 2.9.39
Changed in juju:
milestone: 2.9.39 → 2.9.40
Changed in juju:
milestone: 2.9.40 → 2.9.41
Changed in juju:
milestone: 2.9.41 → 2.9.42
Changed in juju:
milestone: 2.9.42 → 2.9.43
Changed in juju:
milestone: 2.9.43 → 2.9.44
Changed in juju:
milestone: 2.9.44 → 2.9.45
Changed in juju:
milestone: 2.9.45 → 2.9.46
Revision history for this message
Ian Booth (wallyworld) wrote :

The next 2.9.46 candidate release will not include a fix for this bug and we don't plan on any more 2.9 releases. As such it is being removed from its 2.9 milestone.

If the bug is still important to you, let us know and we can consider it for inclusion on a 3.x milestone.

Changed in juju:
milestone: 2.9.46 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.