juju-db.service not updated after mongo-memory-profile change
Bug #1840731 reported by
Paul Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Tim Penhey | ||
Bug Description
We have a number of controllers that had mongo-memory-
Now that we are running Juju 2.6.5, we'd like to switch to "default".
Running "juju controller-config mongo-memory-
* restarted the machine agents
* updated agent.conf on all 3 controllers with "mongomemorypro
However, it did not:
* update juju-db.service
* restart mongod
Shell transcript showing the above: https:/
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Tim Penhey (thumper) |
Revision history for this message
| Tim Penhey (thumper) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → In Progress |
Revision history for this message
| Tim Penhey (thumper) wrote | #3 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| milestone: | none → 2.6.8 |
| Changed in juju: | |
| milestone: | 2.6.8 → 2.6.9 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Very weird. The restart of the agents should have triggered the mongo restart as it rewrote the service config file.