On 02/18/2016 01:07 PM, Jeremy Matthews wrote:
> Hi,
>
> We're having an issue with our cluster where after a reboot of our system a
> location constraint reappears for the ClusterIP. This causes a problem,
> because we have a daemon that checks the cluster state and waits until the
>
Hi,
We're having an issue with our cluster where after a reboot of our system a
location constraint reappears for the ClusterIP. This causes a problem, because
we have a daemon that checks the cluster state and waits until the ClusterIP is
started before it kicks off our application. We didn't
On 02/18/2016 10:40 AM, Christine Caulfield wrote:
> I definitely remember looking into this, or something very like it, ages
> ago. I can't find anything in the commit logs for either corosync or
> cman that looks relevant though. If you're seeing it on recent builds
> then it's obviously still a
