Machines are killed if mongo fails
Bug #1339770 reported by
Jorge Niedbalski
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Ian Booth | ||
1.18 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
If Juju loses connection with mongo, the provisioner can interpret that as being the same as all machines being deleted. This is bad because it then goes and kills all running instances because it thinks they shouldn't be there anymore.
Related to : https:/
tags: | added: landscape maas-provider |
summary: |
- Make provisioner-safe-mode defaults to True on MAAS provider. + Machines are killed if mongo fails |
Changed in juju-core: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | New → In Progress |
tags: | added: canonical-is |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
description: | updated |
no longer affects: | juju-core/1.18 |
To post a comment you must log in.
Juju should not be triggering MAAS release commands just because it goes down even with safe-mode set to False. Are there any details available on what is actually happening?
But I agree that defaulting to True on MAAS is a good first step.