I am trying to place a resource on a remote node with a location constraint
that uses a transient attribute, and this does not work.
The resource is a custom resource script that starts an interface using
networkctl:
primitive router-interface ocf:custom:network_interface params interface=router
The location constraint is:
location router-interface-location router-interface rule router-score: defined
router-ping and router-ping gt 0
(router-ping is set by a ping resource)
The nodes:
charybdis: remote
router-score=6000
skylla: remote
router-score=9000
The transient attributes:
> attrd_updater -A --name router-ping
name="router-ping" host="charybdis" value="100"
name="router-ping" host="skylla" value="100"
CRM simulate output shows that the resource will not be placed anywhere.
crm_simulate -sL -Q
pcmk__primitive_assign: router-interface allocation score on argos: -INFINITY
pcmk__primitive_assign: router-interface allocation score on hestia: -INFINITY
pcmk__primitive_assign: router-interface allocation score on pylon: -INFINITY
If I use only non-transient attributes, the resource will be placed, e.g. the
following places the resource:
location router-interface-location router-interface rule router-score: defined
router-score
But as soon as the location constraint references transient attributes, it will
not work. Pacemaker version is 2.1.8.
Am I doing something wrong here?
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
