Pacemaker allows to create constraints with non-existing node names

Solution In Progress - Updated -

Issue

Cluster takes node names from corosync.conf. When location constraint is created with node name which is not valid (not resolvable/not reachable) constraint gets created anyway without reporting any problem. This may lead to situations where user for example creates cluster with FQDN node names and uses short names in constraint - this will result in constraint being created but ignored.

Following constraints will pass creation but has no effect on resource location:

# pcs constraint location add prefer2 rsc_id invalid_node 100

Environment

  • Red Hat Enterprise Linux 7
  • Pacemaker cluster

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.