04.08.2011 06:08, Andrew Beekhof wrote:
On Wed, Aug 3, 2011 at 7:35 PM, Vladislav Bogdanov bub...@hoster-ok.com
wrote:
01.08.2011 02:05, Andrew Beekhof wrote:
On Wed, Jul 27, 2011 at 11:46 AM, Andrew Beekhof and...@beekhof.net wrote:
On Fri, Jul 1, 2011 at 4:59 PM, Andrew Beekhof
01.08.2011 02:05, Andrew Beekhof wrote:
On Wed, Jul 27, 2011 at 11:46 AM, Andrew Beekhof and...@beekhof.net wrote:
On Fri, Jul 1, 2011 at 4:59 PM, Andrew Beekhof and...@beekhof.net wrote:
Hmm. Interesting. I will investigate.
This is an unfortunate side-effect of my history compression
On Wed, Aug 3, 2011 at 7:35 PM, Vladislav Bogdanov bub...@hoster-ok.com wrote:
01.08.2011 02:05, Andrew Beekhof wrote:
On Wed, Jul 27, 2011 at 11:46 AM, Andrew Beekhof and...@beekhof.net wrote:
On Fri, Jul 1, 2011 at 4:59 PM, Andrew Beekhof and...@beekhof.net wrote:
Hmm. Interesting. I will
On Wed, Jul 27, 2011 at 11:46 AM, Andrew Beekhof and...@beekhof.net wrote:
On Fri, Jul 1, 2011 at 4:59 PM, Andrew Beekhof and...@beekhof.net wrote:
Hmm. Interesting. I will investigate.
This is an unfortunate side-effect of my history compression patch.
Actually I'm mistaken on this. There
On Wed, Jul 27, 2011 at 6:12 PM, Florian Haas florian.h...@linbit.com wrote:
On 2011-07-27 03:46, Andrew Beekhof wrote:
On Fri, Jul 1, 2011 at 4:59 PM, Andrew Beekhof and...@beekhof.net wrote:
Hmm. Interesting. I will investigate.
This is an unfortunate side-effect of my history compression
On 2011-07-27 03:46, Andrew Beekhof wrote:
On Fri, Jul 1, 2011 at 4:59 PM, Andrew Beekhof and...@beekhof.net wrote:
Hmm. Interesting. I will investigate.
This is an unfortunate side-effect of my history compression patch.
Since we only store the last successful and last failed operation,
On Fri, Jul 1, 2011 at 4:59 PM, Andrew Beekhof and...@beekhof.net wrote:
Hmm. Interesting. I will investigate.
This is an unfortunate side-effect of my history compression patch.
Since we only store the last successful and last failed operation, we
don't have the md5 of the start operation
Hi all,
I'm pretty sure I bisected commit which breaks restart of (node local)
resources after definition change.
Nodes which has f59d7460bdde applied (v03-a and v03-b in my case) do not
restart such resources, while node without this commit (mgmt01) does.
Here is snippet from DC (grrr,