Destroying deployed mongodb service fails with 'replica-set-relation-broken'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MongoDB Charm |
In Progress
|
Undecided
|
Mario Splivalo |
Bug Description
When completely removing deployed mongodb service, the unit which is currently 'primary' will not get removed - it will remain stuck in this state:
agent-state-info: 'hook failed: "replica-
This is the excerpt from the log file:
2015-03-24 19:27:18 INFO unit.m7/
2015-03-24 19:27:18 INFO unit.m7/
2015-03-24 19:27:18 INFO unit.m7/
2015-03-24 19:27:18 INFO unit.m7/
2015-03-24 19:27:18 INFO unit.m7/
2015-03-24 19:27:18 INFO unit.m7/
2015-03-24 19:27:18 INFO unit.m7/
2015-03-24 19:27:18 INFO unit.m7/
The workaround is to manually resolve failed unit with 'juju resolved'. After that juju will remove the unit, and completely destroy the service.
Related branches
- Jay Kuri (community): Approve
-
Diff: 96 lines (+29/-21)2 files modifiedhooks/hooks.py (+12/-21)
unit_tests/test_hooks.py (+17/-0)
Changed in mongodb (Juju Charms Collection): | |
assignee: | nobody → Mario Splivalo (mariosplivalo) |
status: | New → Confirmed |
status: | Confirmed → New |
Changed in mongodb (Juju Charms Collection): | |
status: | New → In Progress |
affects: | mongodb (Juju Charms Collection) → mongodb-charm |