09e29800cb
This change is the solution to resolve the scenario where after
an uncontrolled swact due to killing one of the critical processes
twice, the ceph-mon service doesn't start in the new active
controller occasioning a new swact.
It was created a flag to signalize a complete shutdown of ceph-mon.
After an uncontrolled swact, the system verifies if the flag
exists, and if so starts the ceph-mon service in the new active
controller.
Test Plan:
PASS: System host-swact.
PASS: Ceph recovery after rebooting the active controller.
PASS: Ceph recovery after uncontrolled swact killing a critical
process twice.
PASS: Ceph recovery after mgmt network outage for a few minutes
even when rebooting controllers.
PASS: Ceph recovery after case of dead office recovery (DOR).
PASS: Upgrade success from stx 7.0 to 8.0 in a duplex lab.
Closes-bug: 2017133
Signed-off-by: Pedro Vinícius Silva da Cruz <pedro.silvadacruz@windriver.com>
Change-Id: I6784ec76afa3e62ee14e8ca8f3d6c0212a9f6f3e
|
||
|---|---|---|
| .. | ||
| ceph-init-wrapper.sh | ||
| ceph-manage-journal.py | ||
| ceph-mds.conf.pmon | ||
| ceph-preshutdown.sh | ||
| ceph-radosgw.service | ||
| ceph.conf | ||
| ceph.conf.pmon | ||
| ceph.service | ||
| ceph.sh | ||
| mgr-restful-plugin.py | ||
| mgr-restful-plugin.service | ||
| starlingx-docker-override.conf | ||