[2.3, b1] pod commission failed with "Ephemeral operating system ubuntu xenial is unavailable"
Bug #1750891 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Undecided
|
Unassigned |
Bug Description
Our CI hit a failure a couple of times last night where commissioning pods failed with the error message "Ephemeral operating system ubuntu xenial is unavailable":
Command failed: pod compose 1 hostname=juju-1 cores=8 memory=32768 storage=100 zone=1
Ephemeral operating system ubuntu xenial is unavailable.
This occurred at 06:07:35.
However, we know from 'rack-controller list-boot-images' output run shortly before (at 06:06:35) the pod composition that the rack controllers all have the images synced:
http://
We didn't make any changes to image selection between those two times.
I've attached full logs.
This was with maas 2.3.0 (6434-gd354690-
tags: | added: pod |
summary: |
- pod commission failed with "Ephemeral operating system ubuntu xenial is - unavailable" + [2.3] pod commission failed with "Ephemeral operating system ubuntu + xenial is unavailable" |
tags: | added: performance |
Changed in maas: | |
importance: | Undecided → High |
assignee: | nobody → Blake Rouse (blake-rouse) |
milestone: | none → 2.4.0alpha2 |
status: | New → Triaged |
milestone: | 2.4.0alpha2 → none |
Changed in maas: | |
milestone: | none → 2.4.0beta1 |
summary: |
- [2.3] pod commission failed with "Ephemeral operating system ubuntu + [2.3, b1] pod commission failed with "Ephemeral operating system ubuntu xenial is unavailable" |
Changed in maas: | |
assignee: | Blake Rouse (blake-rouse) → nobody |
Changed in maas: | |
milestone: | 2.4.0beta1 → 2.4.0beta2 |
Changed in maas: | |
milestone: | 2.4.0beta2 → 2.4.0rc1 |
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
Changed in maas: | |
status: | Incomplete → Triaged |
Changed in maas: | |
milestone: | 2.4.0rc1 → 2.4.0rc2 |
To post a comment you must log in.
Hi Jason,
So the rack download the images, then update the region and the "cache" on the region side is updated to tell overall that the images are available.
While the rack controllers may already have the images imported, do you have output from the region side that shows whether the images are really fully imported?
For example, does boot-resources read shows "synced" on all before this happens?
Also, are all rack controllers connected? There's the case that rack controllers are not fully connected and these messages are being surfaced?