No actions to stop/start the MON process
Bug #1846049 reported by
Peter Matulis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I do not see any actions that actually stops/starts a Ceph monitor.
Suggested action names and descriptions, based on other bugs:
pause Pause the Ceph monitor service.
resume Resume the Ceph monitor service.
tags: | added: power-events |
summary: |
- No action to stop the MON process + No action to stop/start the MON process |
description: | updated |
description: | updated |
summary: |
- No action to stop/start the MON process + No actions to stop/start the MON process |
description: | updated |
description: | updated |
Changed in charm-ceph-mon: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
To post a comment you must log in.
Not sure if it's related, but for a MON cluster of 3 (ceph-mon/0 , ceph-mon/1, ceph-mon/2),
I stop a service manually:
$ juju ssh ceph-mon/0 sudo systemctl stop ceph-mon.service
and the MON cluster loses quorum and I can no longer query the cluster, as expected.
The output to `juju status` first showed ceph-mon/2 being 'blocked', and followed by units 0 and 1 also being 'blocked'.
However, when I bring back the service:
$ juju ssh ceph-mon/0 sudo systemctl start ceph-mon.service
Units 0 and 1 turn to 'active' while 2 remains 'blocked'.
I can query the cluster successfully:
$ juju ssh ceph-mon/1 sudo ceph status