On 09/11/18 13:24 +, Ian Underhill wrote:
> Yep all my pcs commands run on a live cluster. The design needs
> resources to respond in specific ways before moving on to other
> shutdown requests.
>
> So it seems that these pcs commands that run on different nodes at
> the same time, is the
On Thu, 2018-11-08 at 12:14 +, Ian Underhill wrote:
> seems this issue has been raised before, but has gone quite, with no
> solution
>
> https://lists.clusterlabs.org/pipermail/users/2017-October/006544.htm
> l
In that case, something appeared to be explicitly re-enabling the
disabled
seems this issue has been raised before, but has gone quite, with no
solution
https://lists.clusterlabs.org/pipermail/users/2017-October/006544.html
I know my resource agents successfully return the correct status to the
start\stop\monitor requests
On Thu, Nov 8, 2018 at 11:40 AM Ian Underhill
Sometimes Im seeing that a resource group that is in the process of being
disable is auto restarted by pacemaker.
When issuing pcs disable command to disable different resource groups at
the same time (on different nodes, at the group level) the result is that
sometimes the resource is stopped
