[ClusterLabs] Location not working [FIXED]

Miro Igov miro.igov at pharmya.com
Tue Apr 11 10:31:11 EDT 2023

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




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




From: Users <users-bounces at clusterlabs.org> On Behalf Of Miro Igov
Sent: 10 April 2023 14:19
To: users at clusterlabs.org
Subject: [ClusterLabs] Location not working



I have a resource with location constraint set to:


location intranet-ip_on_any_nginx intranet-ip \

        rule -inf: opa-nginx_1_active eq 0 \

        rule -inf: opa-nginx_2_active eq 0


In syslog I see the attribute transition:

Apr 10 12:11:02 intranet-test2 pacemaker-attrd[1511]:  notice: Setting
opa-nginx_1_active[intranet-test1]: 1 -> 0


Current cluster status is :


Node List:

  * Online: [ intranet-test1 intranet-test2 nas-sync-test1 nas-sync-test2 ]


* stonith-sbd (stonith:external/sbd):  Started intranet-test2

  * admin-ip    (ocf::heartbeat:IPaddr2):        Started nas-sync-test2

  * cron_symlink        (ocf::heartbeat:symlink):        Started

  * intranet-ip (ocf::heartbeat:IPaddr2):        Started intranet-test1

  * mysql_1     (systemd:mariadb at intranet-test1):        Started

  * mysql_2     (systemd:mariadb at intranet-test2):        Started

  * nginx_1     (systemd:nginx at intranet-test1):  Stopped

  * nginx_1_active      (ocf::pacemaker:attribute):      Stopped

  * nginx_2     (systemd:nginx at intranet-test2):  Started intranet-test2

  * nginx_2_active      (ocf::pacemaker:attribute):      Started

  * php_1       (systemd:php5.6-fpm at intranet-test1):     Started

  * php_2       (systemd:php5.6-fpm at intranet-test2):     Started

  * data_1      (ocf::heartbeat:Filesystem):     Stopped

  * data_2      (ocf::heartbeat:Filesystem):     Started intranet-test2

  * nfs_export_1        (ocf::heartbeat:exportfs):       Stopped

  * nfs_export_2        (ocf::heartbeat:exportfs):       Started

  * nfs_server_1        (systemd:nfs-server at nas-sync-test1):     Stopped

  * nfs_server_2        (systemd:nfs-server at nas-sync-test2):     Started


Failed Resource Actions:

  * nfs_server_1_start_0 on nas-sync-test1 'error' (1): call=95,
status='complete', exitreason='', last-rc-change='2023-04-10 12:35:12
+02:00', queued=0ms, exec=209ms



Why intranet-ip is located on intranet-test1 while nginx_1_active is 0 ?


# crm res constraint intranet-ip

(score=INFINITY, id=c_cron_symlink_on_intranet-ip)

* intranet-ip

  : Node nas-sync-test2
(score=-INFINITY, id=intranet-ip_loc-rule)

  : Node nas-sync-test1
(score=-INFINITY, id=intranet-ip_loc-rule)


Why no constraint entry for intranet-ip_on_any_nginx location ?





This message has been sent as a part of discussion between PHARMYA and the
addressee whose name is specified above. Should you receive this message by
mistake, we would be most grateful if you informed us that the message has
been sent to you. In this case, we also ask that you delete this message
from your mailbox, and do not forward it or any part of it to anyone else.
Thank you for your cooperation and understanding.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20230411/ec5a9046/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PharmyaGDPRLogo1.png
Type: image/png
Size: 848 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20230411/ec5a9046/attachment.png>

More information about the Users mailing list