Corosync-notifyd fails to respawn when Corosync is killed

[Alexander Rubtsov]

MOS 9.2 (MU 8)

root@cic-1:/var/log/upstart# service corosync status
corosync start/running, process 3503

root@cic-1:/var/log/upstart# service corosync-notifyd status
corosync-notifyd start/running, process 13409

root@cic-1:/var/log/upstart# ps -ef | grep corosync
root 3503 1 1 22:46 ? 00:00:00 corosync
root 13409 1 0 22:47 ? 00:00:00 corosync-notifyd -d
root 21543 18207 0 22:47 pts/7 00:00:00 grep --color=auto corosync

root@cic-1:/var/log/upstart# kill -9 3503

root@cic-1:/var/log/upstart# ps -ef | grep corosync
root 27544 1 15 22:48 ? 00:00:00 corosync
root 28118 18207 0 22:48 pts/7 00:00:00 grep --color=auto corosync

root@cic-1:/var/log/upstart# dmesg | tail -30
[2675206.212138] init: corosync main process (3503) killed by KILL signal
[2675206.212153] init: corosync main process ended, respawning
[2675206.214291] init: pacemaker main process (3842) terminated with status 107
[2675206.214309] init: pacemaker main process ended, respawning
[2675206.217325] init: corosync-notifyd main process ended, respawning
[2675206.232314] init: corosync-notifyd main process (27506) terminated with status 1
[2675206.232325] init: corosync-notifyd main process ended, respawning
[2675206.244528] init: corosync-notifyd main process (27519) terminated with status 1
[2675206.244540] init: corosync-notifyd main process ended, respawning
[2675206.256144] init: corosync-notifyd main process (27529) terminated with status 1
[2675206.256156] init: corosync-notifyd main process ended, respawning
[2675206.269303] init: corosync-notifyd main process (27540) terminated with status 1
[2675206.269315] init: corosync-notifyd main process ended, respawning
[2675206.281567] init: corosync-notifyd main process (27553) terminated with status 1
[2675206.281585] init: corosync-notifyd main process ended, respawning
[2675206.293058] init: corosync-notifyd main process (27564) terminated with status 1
[2675206.293073] init: corosync-notifyd main process ended, respawning
[2675206.308207] init: corosync-notifyd main process (27578) terminated with status 1
[2675206.308223] init: corosync-notifyd main process ended, respawning
[2675206.320216] init: corosync-notifyd main process (27586) terminated with status 1
[2675206.320231] init: corosync-notifyd main process ended, respawning
[2675206.332705] init: corosync-notifyd main process (27594) terminated with status 1
[2675206.332722] init: corosync-notifyd main process ended, respawning
[2675206.345813] init: corosync-notifyd main process (27608) terminated with status 1
[2675206.345831] init: corosync-notifyd respawning too fast, stopped

[Alexander Rubtsov (arubtsov)]

sla2 for 9.0-updates

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: 9.0
Change author: Roman Lubianyi <email address hidden>
Review: https://review.fuel-infra.org/40806

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/40806
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0

Commit: d2e507c4ce348d5937c09e39f37c971ce1dbe972
Author: Roman Lubianyi <email address hidden>
Date: Wed Mar 20 13:00:42 2019

Increase respawn limit for corosync-notifyd.

When corosync is killed the default respawn limit
for corosync-notifyd not enough for successfully
respawn and reconnect to corosync API.

Change-Id: I1453d3e2bc832e01dff612b39958baa42e71d1ac
Closes-Bug: #1820804

[Pavel Glazov (pglazovv)]

Verified