setting and unsetting standby node state leaves -INFINITY constraint for...
Brought to you by:
rastol
I think this just started occurring in v1.5.1. Now when I set a node standby and then online it again, a -INFINITY host location constraint is left on linbit:drbd master/slave resources. OS is CentOS 6.4.
Does it come from resource level fencing? In the next LCMC version, the fenced resources will be made more obvious.
That is definitely possible. I do have resource-only fencing enabled for the DRBD global settings. Also maybe there is an issue with the crm tool and CentOS 6.4 because I think I have seen this problem using "crm node standby" as well. It works correctly with "pcs cluster standby".
are you still having this problem? Only difference is that pcs removes the stand-by attribute, whereas LCMC and crmsh set this to "off". That shouldn't make any difference.
It looks like you were right about where this problem came from. Now that I have 1.5.6, I'm seeing that the drbd objects with the -infinity constraint say fenced next to them. So that new visual notification really helps. I guess I need to figure out why my drbd resources aren't clearing the fencing automatically…
Thanks!
Doug
On Jul 11, 2013, at 10:19 PM, Rasto Levrinc rastol@users.sf.net wrote:
Related
Bugs: #14