On Tue, Apr 11, 2023 at 6:27 PM Ken Gaillot <kgail...@redhat.com> wrote: > > On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote: > > I fixed the issue by changing location definition from: > > > > location intranet-ip_on_any_nginx intranet-ip \ > > rule -inf: opa-nginx_1_active eq 0 \ > > rule -inf: opa-nginx_2_active eq 0 > > > > To: > > > > location intranet-ip_on_any_nginx intranet-ip \ > > rule opa-nginx_1_active eq 1 \ > > rule opa-nginx_2_active eq 1 > > > > Now it works fine and shows the constraint with: crm res constraint > > intranet-ip > > Ah, I suspect the issue was that the original constraint compared only > against 0, when initially (before the resources ever start) the > attribute is undefined. >
This does not really explain the original question. Apparently the attribute *was* defined but somehow ignored. Apr 10 12:11:02 intranet-test2 pacemaker-attrd[1511]: notice: Setting opa-nginx_1_active[intranet-test1]: 1 -> 0 ... * intranet-ip (ocf::heartbeat:IPaddr2): Started intranet-test1 _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/