[Debian-ha-maintainers] Accepted corosync-qdevice 3.0.0-2 (source) into unstable

[Valentin Vidic]

On Fri, Feb 01, 2019 at 09:35:40AM +0100, Valentin Vidic wrote:
> Sure, here it goes...

It seems that qdevice test has started to fail already with corosync
3.0.1 because the corosync service is not running. And indeed after
installing the corosync package the corosync.service is started but
stops right away. I guess this is related to the StopWhenUnneeded=yes
added in corosync 3.0.1. What do you think about this change?

Feb  2 11:45:58 node1 systemd[1]: Starting Corosync Cluster Engine...
Feb  2 11:45:58 node1 corosync[26073]:   [MAIN  ] Corosync Cluster Engine 3.0.1 starting up
Feb  2 11:45:58 node1 corosync[26073]:   [MAIN  ] Corosync built-in features: dbus monitoring watchdog augeas systemd xmlconf snmp pie relro bindnow
Feb  2 11:45:58 node1 corosync[26073]:   [TOTEM ] Initializing transport (Kronosnet).
Feb  2 11:45:58 node1 corosync[26073]:   [TOTEM ] totemknet initialized
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync configuration map access [0]
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] server name: cmap
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync configuration service [1]
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] server name: cfg
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] server name: cpg
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync profile loading service [4]
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync resource monitoring service [6]
Feb  2 11:45:58 node1 corosync[26073]:   [WD    ] Watchdog not enabled by configuration
Feb  2 11:45:58 node1 corosync[26073]:   [WD    ] resource load_15min missing a recovery key.
Feb  2 11:45:58 node1 corosync[26073]:   [WD    ] resource memory_used missing a recovery key.
Feb  2 11:45:58 node1 corosync[26073]:   [WD    ] no resources configured.
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync watchdog service [7]
Feb  2 11:45:58 node1 corosync[26073]:   [QUORUM] Using quorum provider corosync_votequorum
Feb  2 11:45:58 node1 corosync[26073]:   [QUORUM] This node is within the primary component and will provide service.
Feb  2 11:45:58 node1 corosync[26073]:   [QUORUM] Members[0]:
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] server name: votequorum
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] server name: quorum
Feb  2 11:45:58 node1 corosync[26073]:   [KNET  ] host: host: 1 has no active links
Feb  2 11:45:58 node1 systemd[1]: Started Corosync Cluster Engine.
Feb  2 11:45:58 node1 corosync[26073]:   [TOTEM ] A new membership (1:4) was formed. Members joined: 1
Feb  2 11:45:58 node1 corosync[26073]:   [CPG   ] downlist left_list: 0 received
Feb  2 11:45:58 node1 corosync[26073]:   [QUORUM] Members[1]: 1
Feb  2 11:45:58 node1 corosync[26073]:   [MAIN  ] Completed service synchronization, ready to provide service.
Feb  2 11:45:58 node1 corosync[26073]:   [MAIN  ] Node was shut down by a signal
Feb  2 11:45:58 node1 systemd[1]: Stopping Corosync Cluster Engine...
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Unloading all Corosync service engines.
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] withdrawing server sockets
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync vote quorum service v1.0
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] withdrawing server sockets
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync configuration map access
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] withdrawing server sockets
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync configuration service
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] withdrawing server sockets
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync cluster closed process group service v1.01
Feb  2 11:45:58 node1 corosync[26073]:   [QB    ] withdrawing server sockets
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync cluster quorum service v0.1
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync profile loading service
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync resource monitoring service
Feb  2 11:45:58 node1 corosync[26073]:   [SERV  ] Service engine unloaded: corosync watchdog service
Feb  2 11:45:58 node1 corosync[26073]:   [KNET  ] host: host: 1 has no active links
Feb  2 11:45:58 node1 corosync[26073]:   [MAIN  ] Corosync Cluster Engine exiting normally
Feb  2 11:45:58 node1 systemd[1]: corosync.service: Succeeded.
Feb  2 11:45:58 node1 systemd[1]: Stopped Corosync Cluster Engine.

-- 
Valentin