Updating controller name shouldn't be allowed in the UI
Bug #1871605 reported by
Alberto Donato
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Unassigned | ||
| maas-ui |
Fix Released
|
Unknown
|
|||
Bug Description
MAAS doesn't really support updating hostname for a controller.
The UI currently allows it but the change has no effect, the result returned by the controller.update websocket call still has the previous hostname.
We shouldn't let users change hostname for the controller.
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in maas-ui: | |
| status: | Unknown → New |
| Changed in maas-ui: | |
| status: | New → Fix Released |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| milestone: | none → 3.3.0 |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.3.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I wonder if we should prevent the name/hostname of Pods from being updated as well. Currently we let users change the name which is committed to the database but it doesn't actually change the name of the remote host.