Creating KVM or RSD error references pods
Bug #1832480 reported by
Steve Rydz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.5 |
Won't Fix
|
Low
|
Unassigned | |||
3.6 |
Triaged
|
Low
|
Unassigned |
Bug Description
When creating a new KVM or RSD, if there is an error, for example a timeout or incorrect address, the error message references pods, e.g:
"Failed talking to pod: The label b'qemu+ssh' is not a valid A-label"
or
"Failed talking to pod: User timeout caused connection failure."
As pod has been renamed to KVM this error needs to read: "Failed talking to KVM" if a KVM is being created or if a RSD is being created it should read: "Failed talking to RSD".
This string doesn't look like it's something that can be changed via the front-end.
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
milestone: | 2.7.0b1 → 2.7.0b2 |
Changed in maas: | |
milestone: | 2.7.0b2 → none |
Changed in maas: | |
importance: | Medium → Low |
milestone: | none → 3.5.0 |
Changed in maas: | |
milestone: | 3.5.0 → 3.5.x |
To post a comment you must log in.
This is because the backend doesn’t have the differentiation between KVM and RSD, and the API is done everything under “pod”.
This is why this transition should have been planned both from the backend and the UI and not the UI. We currently don’t have in roadmap to transition all of this!