Attempting to deploy an image that is still syncing gives a non-specific error
Bug #1834403 reported by
Trent Lloyd
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Medium
|
Unassigned | ||
| 3.5 |
Won't Fix
|
Medium
|
Unassigned | ||
| 3.6 |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Trying to deploy a custom image that is still deploying, gives a non-specific error:
2019-06-27 12:08:01 maasserver.
The same non-specific error appears in the Web UI.
Ideally the error would indicate why the deployment is not available. This happened when trying to deploy a freshly imported custom image (5GB) - it takes 5-10 minutes to sync at least on my testing setup and could be an easy place for new users to get stuck.
Tested on 2.5.3-7533-
| description: | updated |
| Changed in maas: | |
| milestone: | none → 2.7.0alpha1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | 2.7.0alpha1 → none |
Revision history for this message
| Adam Collard (adam-collard) wrote | #1 |
| tags: | added: image-in-db |
| Changed in maas: | |
| milestone: | none → 3.5.0 |
| Changed in maas: | |
| milestone: | 3.5.0 → 3.5.x |
| Changed in maas: | |
| milestone: | 3.6.x → 3.7.x |
To post a comment you must log in.
This should be addressed in upcoming work for this cycle to rework image storage