[maas] juju set-env fails after upgrading to 1.16.2+
Bug #1256179 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
John A Meinel | ||
| 1.16 |
Fix Released
|
Critical
|
John A Meinel | ||
| juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Saucy |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
The 1.16.2 release fixed a critical issue with the MAAS provider where Juju would destroy instances that were not part of the Juju environment. Part of the fix involved adding a new config setting, maas-agent-name.
After upgrading, juju set-env fails with an error message about not being able to change maas-agent-name. It doesn't exist in state, and the new default is ""; i.e. we can't change from nil to "".
As a workaround, one can do:
$ mongo --ssl -u admin -p <admin-secret> localhost:
> use juju
> db.settings.
> db.settings.
Related branches
lp://staging/~jameinel/juju-core/1.16-set-env-maas-name-1256179
- Juju Engineering: Pending requested
-
Diff: 345 lines (+230/-59)5 files modifiedprovider/maas/config.go (+10/-1)
provider/maas/environ_test.go (+197/-0)
provider/maas/environ_whitebox_test.go (+0/-52)
provider/maas/export_test.go (+23/-0)
provider/maas/maas_test.go (+0/-6)
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju-core: | |
| milestone: | none → 1.17.1 |
| Changed in juju-core: | |
| assignee: | nobody → John A Meinel (jameinel) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| milestone: | 1.17.1 → 1.17.0 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| tags: | added: maas-provider regression |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Changed in juju-core (Ubuntu): | |
| status: | New → Fix Released |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #2 |
| Changed in juju-core (Ubuntu Saucy): | |
| status: | New → Won't Fix |
To post a comment you must log in.
Bumping this up to critical for 1.16.5 because anyone upgrading from <1.16.2 to >=1.16.2 is going to run into this.