machine-0 agent needs admin rights during upgrade
Bug #1306902 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
In juju <=1.18.0 machine-0 agent did not need admin rights. However, to configure Replica Set details we need to have admin rights.
Since we don't have any agents with admin rights, we need to stop mongo, bring it up without --auth, change the auth for machine-0 to be in the admin group, and then bring mongo back up as usual.
This probably needs to be an upgrade step, and we'll need some care because everything will want to bounce if mongo doesn't have a stable connection.
Related branches
lp:~axwalk/juju-core/lp1306902-mongo-ensureadminuser
- Juju Engineering: Pending requested
-
Diff: 433 lines (+258/-48)7 files modifiedagent/mongo/mongo.go (+24/-0)
agent/mongo/mongo_test.go (+55/-0)
agent/mongo/upgrade.go (+101/-0)
cmd/jujud/machine.go (+42/-6)
cmd/jujud/machine_test.go (+34/-0)
state/compat_test.go (+0/-32)
state/open.go (+2/-10)
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| Changed in juju-core: | |
| milestone: | none → 1.19.1 |
| milestone: | 1.19.1 → 1.19.0 |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
