Cannot deploy with newly synced images
Bug #1964143 reported by
Anton Smith
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Medium
|
Unassigned | ||
| 3.3 |
Triaged
|
Medium
|
Unassigned | ||
| maas-ui |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
After syncing a new image (i.e. selecting 21.10), I can't deploy it.
Reloading/
| tags: | added: ui |
| Changed in maas-ui: | |
| importance: | Undecided → Unknown |
| summary: |
- Cannot deploy with newly synced images + UI: Cannot deploy with newly synced images |
| summary: |
- UI: Cannot deploy with newly synced images + Cannot deploy with newly synced images |
| Changed in maas-ui: | |
| importance: | Unknown → Undecided |
| status: | New → Invalid |
Revision history for this message
| Jerzy Husakowski (jhusakowski) wrote | #2 |
| Changed in maas: | |
| importance: | Undecided → Medium |
| milestone: | none → 3.3.0 |
| status: | New → Triaged |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.4.0 |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.x |
To post a comment you must log in.
The issue is that the list of deployable images need to be explicitly fetched from the API because the "general" websocket API endpoint does not have notifiers set up. The quick fix would be to fetch this list every time the user comes across a part of the UI that needs it, but the better fix would be to have websocket notifiers set up so we don't have to.
https:/