kvm-based units are ignoring container-image-metadata-url
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Achilleas Anagnostopoulos | ||
2.8 |
Fix Released
|
High
|
Achilleas Anagnostopoulos |
Bug Description
Juju 2.7
Ubuntu 19.10
Units deployed using kvm are ignoring container-
It also appears that kvm provisioning requires index.sjson rather than index.json as with lxd provisioned units
This makes deploying kvm-based units extremely slow or impossible to deploy if on isolated network
Units deployed using lxd are respecting this setting.
Juju status:
0 started 172.27.21.120 node03ob20 bionic default Deployed
0/kvm/0 pending pending eoan copying http://
0/lxd/0 started 172.27.21.127 juju-1e08fb-0-lxd-0 bionic default Container started
Juju model-config:
agent-metadata-url controller https:/
container-
image-metadata-url controller https:/
Juju debug-log:
Only log message related to provisioning kvm-based units and kvm images is:
machine-1: 19:59:52 DEBUG juju.container.kvm synchronise images for amd64 eoan released https:/
LXD finds image:
machine-0: 19:59:08 DEBUG juju.container.lxd Found image remotely - "cloud-
local simple-streams product images shows the required image and image is on disk:
curl -sSlL https:/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
curl -sSlL https:/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
"path": "server/
tags: | added: cpe-onsite |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
assignee: | nobody → Achilleas Anagnostopoulos (achilleasa) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Apparently this is also happening in 2.6.10 based juju deployment. image-metadata- url model-config value, but the KVMs are going over proxy + cloud-images. ubuntu. com
LXD images are respecting the container-