Juju can't find KVM images for arm64 focal

Bug #1990682 reported by Bas de Bruijne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Joseph Phillips

Bug Description

In testrun https://solutions.qa.canonical.com/testruns/testRun/66cfff7a-8dd3-43bf-9c2f-fd26071d4467, which is on an arm64 lab on focal, fails with:

```
Machine State Address Inst id Series AZ Message
0 started 10.246.200.106 sqa-lab2-node-1-arm focal zone1 Deployed
0/lxd/0 started 10.246.200.210 juju-91e9d3-0-lxd-0 focal zone1 Container started
1 started 10.246.200.107 sqa-lab2-node-2-arm focal zone2 Deployed
1/lxd/0 started 10.246.200.209 juju-91e9d3-1-lxd-0 focal zone2 Container started
1/lxd/1 started 10.246.200.208 juju-91e9d3-1-lxd-1 focal zone2 Container started
2 started 10.246.200.105 sqa-lab2-node-3-arm focal zone3 Deployed
2/lxd/0 started 10.246.200.212 juju-91e9d3-2-lxd-0 focal zone3 Container started
2/lxd/1 started 10.246.200.213 juju-91e9d3-2-lxd-1 focal zone3 Container started
3 started 10.246.200.108 sqa-lab2-node-4-arm focal zone1 Deployed
3/lxd/0 started 10.246.200.207 juju-91e9d3-3-lxd-0 focal zone1 Container started
4 started 10.246.200.109 sqa-lab2-node-6-arm focal zone3 Deployed
4/lxd/0 started 10.246.200.214 juju-91e9d3-4-lxd-0 focal zone3 Container started
5 started 10.246.200.200 sqa-lab2-node-7-arm focal zone1 Deployed
5/kvm/0 down pending focal no results for "arm64", "focal", "released", "uefi1.img"
5/lxd/0 started 10.246.200.211 juju-91e9d3-5-lxd-0 focal zone1 Container started
5/lxd/1 started 10.246.200.217 juju-91e9d3-5-lxd-1 focal zone1 Container started
6 started 10.246.200.110 sqa-lab2-node-8-arm focal zone2 Deployed
6/lxd/0 started 10.246.200.205 juju-91e9d3-6-lxd-0 focal zone2 Container started
6/lxd/1 started 10.246.200.206 juju-91e9d3-6-lxd-1 focal zone2 Container started
7 started 10.246.200.203 sqa-lab2-node-9-arm focal zone3 Deployed
7/kvm/0 down pending focal no results for "arm64", "focal", "released", "uefi1.img"
7/lxd/0 started 10.246.200.215 juju-91e9d3-7-lxd-0 focal zone3 Container started
7/lxd/1 started 10.246.200.216 juju-91e9d3-7-lxd-1 focal zone3 Container started
8 started 10.246.200.201 vault-1 focal zone1 Deployed
9 started 10.246.200.204 vault-2 focal zone2 Deployed
10 started 10.246.200.202 vault-3 focal zone3 Deployed
```

I think this is an issue from Juju, but I'm not sure.

Configs and crashdumps can be found here:
https://oil-jenkins.canonical.com/artifacts/66cfff7a-8dd3-43bf-9c2f-fd26071d4467/index.html

Revision history for this message
Marian Gasparovic (marosg) wrote :

just to be clear, it happens only for KVM machines

Revision history for this message
Joseph Phillips (manadart) wrote :

Are you pro-actively using any config for container-image-metadata-url or container-image-stream?

Or are you letting it use defaults?

Changed in juju:
status: New → Incomplete
importance: Undecided → High
assignee: nobody → Joseph Phillips (manadart)
Revision history for this message
Alexander Balderson (asbalderson) wrote :

we're just using the defaults.

Changed in juju:
status: Incomplete → New
Revision history for this message
Marian Gasparovic (marosg) wrote :

I did some digging. Latest uefi1.img images are for 16.04
It looks like since 19.10 disk-kvm.img started to appear but not for arm64

Revision history for this message
Marian Gasparovic (marosg) wrote :

After a chat with Public Cloud, disk1.img is what is needed

uefi1.img was xenial specific, here is some reasoning
https://git.launchpad.net/simplestreams/commit/?id=d7f16037389c9155dd4d48279eea4cc0ca198cd1

Changed in juju:
status: New → In Progress
Changed in juju:
status: In Progress → Fix Committed
milestone: none → 2.9.36
Revision history for this message
Joseph Phillips (manadart) wrote :
Changed in juju:
status: Fix Committed → Fix Released
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.