handle cloud region rename in running controller
Bug #1871729 reported by
Christian Muirhead
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
panda posted on discourse that a datacenter had been renamed in their vSphere cloud and they wanted to update the controller to match.
https:/
It looks like we can update the cloud's regions (since the vSphere datacenter maps to a region in Juju) using `update-cloud --controller` but there doesn't seem to be any way to update a model's region other than directly in mongo.
It doesn't seem like this problem would be specific to vSphere, although it's easy for it to occur there.
Revision history for this message
| Christian Muirhead (2-xtian) wrote | #1 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Undecided → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Workaround to update the model's cloud-region in the database.
https:/