On 2013-12-06T09:54:19, Gaëtan Slongo wrote:
> I know this is caused by the "-inf" but I don't explicitly created this
> constraint ... Pacemaker did it himself... :-(
No, it did this because you *asked it to*.
> This constraint is also created when the resource moves automatically.
No. This i
Hi !
I know this is caused by the "-inf" but I don't explicitly created this
constraint ... Pacemaker did it himself... :-(
This constraint is also created when the resource moves automatically.
Then after a successfuly (and automatic) "move" the resource is
"blocked" on the current node until I
On 2013-12-06T09:00:32, Gaëtan Slongo wrote:
> OK I understand, but this makes troubles for me... Example: When the
> node holding the resource (and the constraint) reboots the resource is
> not moving to the other node (because of this constraint, I see on the
> debug logs no node can hold the r
Hi
Thank you for your answer.
OK I understand, but this makes troubles for me... Example: When the
node holding the resource (and the constraint) reboots the resource is
not moving to the other node (because of this constraint, I see on the
debug logs no node can hold the resource). As soon as I r
On 2013-12-05T17:12:01, Gaëtan Slongo wrote:
> Hi !
>
> I'm trying to configure a cluster using pacemaker 1.1 and corosync since
> 2 days (on Debian wheezy). Many of my current problems are related to
> the contraint creation. When I manually move a resource (or when a
> failback occurs) this ki
Hi !
I'm trying to configure a cluster using pacemaker 1.1 and corosync since
2 days (on Debian wheezy). Many of my current problems are related to
the contraint creation. When I manually move a resource (or when a
failback occurs) this kind of constraint is automatically created :
location cli-s
