`juju status` shows LXD VMs as containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Jack Shaw |
Bug Description
It's a small thing but some Juju messages are referring to LXD VMs as being containers:
```
$ juju add-machine --constraints=
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
microarm overlord microcloud-
Machine State Address Inst id Base AZ Message
7 pending juju-24971e-7 ubuntu@22.04 Container started
$ juju debug-log --level DEBUG --replay | grep -F juju-24971e-7
controller-0: 09:46:15 INFO juju.worker.
controller-0: 09:46:25 INFO juju.worker.
controller-0: 09:46:25 INFO juju.worker.
controller-0: 09:47:59 INFO juju.worker.
controller-0: 09:49:01 INFO juju.worker.
```
But that juju-24971e-7 instance is indeed a virtual machine:
```
$ lxc ls microcloud:
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | LOCATION |
+------
| juju-24971e-7 | RUNNING | 10.92.44.3 (eth0) | fd42:6f75:
+------
```
Additional information:
```
$ snap list juju
Name Version Rev Tracking Publisher Notes
juju 3.1.0 22136 3.1/stable canonical✓ -
```
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Jack Shaw (jack-shaw) |