1 corosync (3.1.2-pve1) pve; urgency=medium
3 * update to Corosync 3.1.2
5 -- Proxmox Support Team <support@proxmox.com> Tue, 6 Apr 2021 14:25:27 +0200
7 corosync (3.1.0-pve1) pve; urgency=medium
9 * update to Corosync 3.1.0
10 + Configuration system is rewritten and reload became atomic operation.
11 + Quorum service got improved API with ability to register new totem
12 members change callback.
13 + Default token timeout was changed from 1 seconds to 3 seconds.
14 + Support for changing crypto configuration during runtime.
16 -- Proxmox Support Team <support@proxmox.com> Thu, 28 Jan 2021 11:39:25 +0100
18 corosync (3.0.4-pve1) pve; urgency=medium
20 * update to Corosync 3.0.4
22 -- Proxmox Support Team <support@proxmox.com> Thu, 25 Jun 2020 17:02:11 +0200
24 corosync (3.0.3-pve1) pve; urgency=medium
26 * update to Corosync 3.0.3
28 -- Proxmox Support Team <support@proxmox.com> Mon, 25 Nov 2019 15:38:52 +0100
30 corosync (3.0.2-pve4) pve; urgency=medium
32 * backport a fix ensuring that the messages during recovery (retransmission)
33 do not exceed the maximum possible KNET package size.
35 -- Proxmox Support Team <support@proxmox.com> Thu, 10 Oct 2019 18:16:02 +0200
37 corosync (3.0.2-pve3) pve; urgency=medium
39 * totemknet: Disable forwarding on shutdown to make knet flush all messages
40 (especially LEAVE one)
42 * totemknet: Add locking for log call to ensure no log message is lost from
45 * totempg: Check sanity (length) of received message
47 -- Proxmox Support Team <support@proxmox.com> Thu, 03 Oct 2019 16:13:54 +0200
49 corosync (3.0.2-pve2) pve; urgency=medium
51 * cherry pick totem config patches to improve compatibillity with setups
52 without a (currently) configured link0
54 -- Proxmox Support Team <support@proxmox.com> Fri, 21 Jun 2019 14:26:28 +0200
56 corosync (3.0.2-pve1) pve; urgency=medium
58 * update to Corosync 3.0.2
60 -- Proxmox Support Team <support@proxmox.com> Wed, 19 Jun 2019 13:47:17 +0200
62 corosync (3.0.1-pve1) pve; urgency=medium
64 * update to Corosync 3.0.1-2
66 * cherry-pick crypto changes for upgrade compatibility
68 * cherry-pick CPG callback joinlist merging (PR 468)
70 * drop transitional corosync-pve/libcorosync4-pve packages
72 * corosync-qdevice/corosync-qnetd are now shipped separately
74 * drop discontinued libtotem-pq library packages
76 -- Proxmox Support Team <support@proxmox.com> Wed, 22 May 2019 12:40:27 +0200
78 corosync (2.4.4-pve1) unstable; urgency=medium
80 * update to corosync 2.4.4
82 -- Proxmox Support Team <support@proxmox.com> Wed, 24 Oct 2018 12:48:36 +0200
84 corosync (2.4.2-pve5) unstable; urgency=medium
86 * cpg: Inform clients about left nodes during pause
88 -- Proxmox Support Team <support@proxmox.com> Wed, 25 Apr 2018 10:26:48 +0200
90 corosync (2.4.2-pve4) unstable; urgency=medium
94 -- Proxmox Support Team <support@proxmox.com> Fri, 13 Apr 2018 10:29:34 +0200
96 corosync (2.4.2-pve3) unstable; urgency=medium
98 * don't install corosync-qdevice init script
100 -- Proxmox Support Team <support@proxmox.com> Thu, 8 Jun 2017 14:13:22 +0200
102 corosync (2.4.2-pve2) unstable; urgency=medium
104 * add libcorosync4-pve transitional package
106 * only start corosync service if config exists
108 -- Proxmox Support Team <support@proxmox.com> Mon, 13 Mar 2017 13:31:34 +0100
110 corosync (2.4.2-pve1) unstable; urgency=medium
112 * switch to Debian's corosync package as base
114 -- Proxmox Support Team <support@proxmox.com> Wed, 8 Mar 2017 14:16:58 +0100
116 corosync-pve (2.4.2-2) unstable; urgency=medium
118 * rebuild for PVE 5.0 / Debian Stretch
120 -- Proxmox Support Team <support@proxmox.com> Mon, 6 Mar 2017 09:30:57 +0100
122 corosync-pve (2.4.2-1) unstable; urgency=medium
124 * update to corosync 2.4.2
126 -- Proxmox Support Team <support@proxmox.com> Wed, 08 Feb 2017 14:08:49 +0100
128 corosync-pve (2.4.0-1) unstable; urgency=medium
132 -- Proxmox Support Team <support@proxmox.com> Sat, 16 Jul 2016 10:27:49 +0200
134 corosync-pve (2.3.5-2) unstable; urgency=medium
136 * update to latest versions from branch needle
137 (commit e2b6b25126a3e8f2caefcb8ccde67788c63fbeb5)
139 * remove patch 0001-totem-swap-unicast-and-multicast-bind-order.patch (upstream)
141 -- Proxmox Support Team <support@proxmox.com> Thu, 03 Dec 2015 14:49:43 +0100
143 corosync-pve (2.3.5-1) unstable; urgency=medium
147 -- Proxmox Support Team <support@proxmox.com> Mon, 21 Sep 2015 12:02:49 +0200
149 corosync-pve (2.3.4-2) unstable; urgency=medium
151 * update to latest upstream (commit 82526d2fe9137e8b604f1bbae6d6e39ba41377f9)
153 -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2015 19:10:35 +0200
155 corosync-pve (2.3.4-1) unstable; urgency=medium
159 * recompile for Debian Jessie
161 -- Proxmox Support Team <support@proxmox.com> Mon, 23 Feb 2015 08:20:52 +0100
163 corosync-pve (1.4.7-1) unstable; urgency=low
167 -- Proxmox Support Team <support@proxmox.com> Tue, 22 Jul 2014 06:17:13 +0200
169 corosync-pve (1.4.6-1) unstable; urgency=low
173 -- Proxmox Support Team <support@proxmox.com> Fri, 09 May 2014 07:14:06 +0200
175 corosync-pve (1.4.5-1) unstable; urgency=low
179 -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 06:35:02 +0100
181 corosync-pve (1.4.4-3) unstable; urgency=low
183 * run at high priority using setpriority(-20)
185 -- Proxmox Support Team <support@proxmox.com> Tue, 15 Jan 2013 12:54:02 +0100
187 corosync-pve (1.4.4-2) unstable; urgency=low
189 * disable SCHED_RR (RT_GROUP_SCHED was disabled in our kernel
190 anyways). In newer kernels this is enabled, but causes corosync to
193 -- Proxmox Support Team <support@proxmox.com> Fri, 11 Jan 2013 15:39:40 +0100
195 corosync-pve (1.4.4-1) unstable; urgency=low
199 -- Proxmox Support Team <support@proxmox.com> Tue, 02 Oct 2012 09:41:59 +0200
201 corosync-pve (1.4.3-1) unstable; urgency=low
205 -- Proxmox Support Team <support@proxmox.com> Thu, 12 Apr 2012 12:54:10 +0200
207 corosync-pve (1.4.1-1) unstable; urgency=low
211 -- Proxmox Support Team <support@proxmox.com> Tue, 26 Jul 2011 11:49:17 +0200
213 corosync-pve (1.4.0-1) unstable; urgency=low
217 * remove fix-schedrr-warning.patch (alread in 1.4.0)
219 -- Proxmox Support Team <support@proxmox.com> Tue, 19 Jul 2011 12:36:54 +0200
221 corosync-pve (1.3.1-1) unstable; urgency=low
223 * update to latest stable
225 -- Proxmox Support Team <support@proxmox.com> Thu, 23 Jun 2011 06:52:20 +0200
227 corosync-pve (1.3.0-1) unstable; urgency=low
229 * update to latest stable
231 -- Proxmox Support Team <support@proxmox.com> Thu, 02 Dec 2010 07:11:10 +0100
233 corosync-pve (1.2.8-1) unstable; urgency=low
235 * update to latest stable
237 -- Proxmox Support Team <support@proxmox.com> Wed, 06 Oct 2010 13:24:24 +0200
239 corosync-pve (1.2.0-1) unstable; urgency=low
241 * add patches/cpg-join-fix.diff, see
242 https://bugzilla.redhat.com/show_bug.cgi?id=568356
244 * update to latest stable
246 * do not create/installe /etc/corosync/* - we use cman instead
248 * delete init.d script - we use cman instead
250 -- Proxmox Support Team <support@proxmox.com> Thu, 21 Jan 2010 13:50:43 +0100
252 corosync-pve (1.1.2-1) unstable; urgency=low
254 * update to latest stable
256 -- Proxmox Support Team <support@proxmox.com> Fri, 23 Oct 2009 11:41:04 +0200
258 corosync-pve (1.1.1-1) unstable; urgency=low
260 * update to latest stable
262 -- Proxmox Support Team <support@proxmox.com> Thu, 22 Oct 2009 12:46:53 +0200
264 corosync-pve (1.0-1) unstable; urgency=low
266 * update to latest trunc
268 * use quilt instead of dpatch
270 * use /dev/urandom instead of /dev/random for key generation
272 * new config file localtion: /etc/corosync/corosync.conf
274 * new key location: /etc/corosync/authkey
276 * new default configuration: secauth = on
278 * auto-generate authkey in postinst script if it does not exist
280 -- Proxmox Support Team <support@proxmox.com> Mon, 08 Jun 2009 03:28:34 -0400
282 corosync-pve (0.95-1) unstable; urgency=low
286 -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2009 10:07:13 -0400
288 corosync-pve (0.94-1) unstable; urgency=low
292 -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2009 06:55:24 -0400