ALT Linux Bugzilla – #41546

Created attachment 10052 [details]
Скрин Web-интерфейса кластера

При поднятии кластера, на Альт Сервер 9.2, разрозненная информация веб-интерфейса и вывода статуса в консоли. В Ubuntu с этой же конфигурацией всё нормально было.

Конфигурация кластера:
pcs config
Cluster Name: pg_cluster
Corosync Nodes:
 linux-db1 linux-db2
Pacemaker Nodes:
 linux-db1 linux-db2

Resources:
 Clone: pgsqld-clone
  Meta Attrs: notify=true promotable=true
  Resource: pgsqld (class=ocf provider=heartbeat type=pgsqlms)
   Operations: demote interval=0s timeout=120s (pgsqld-demote-interval-0s)
               methods interval=0s timeout=5 (pgsqld-methods-interval-0s)
               monitor interval=15s role=Master timeout=10s (pgsqld-monitor-interval-15s)
               monitor interval=16s role=Slave timeout=10s (pgsqld-monitor-interval-16s)
               notify interval=0s timeout=60s (pgsqld-notify-interval-0s)
               promote interval=0s timeout=30s (pgsqld-promote-interval-0s)
               reload interval=0s timeout=20 (pgsqld-reload-interval-0s)
               start interval=0s timeout=60s (pgsqld-start-interval-0s)
               stop interval=0s timeout=60s (pgsqld-stop-interval-0s)
 Resource: ip-virtual (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=110.14.132.117
  Operations: monitor interval=10s (ip-virtual-monitor-interval-10s)
              start interval=0s timeout=20s (ip-virtual-start-interval-0s)
              stop interval=0s timeout=20s (ip-virtual-stop-interval-0s)

Stonith Devices:
Fencing Levels:

Location Constraints:
Ordering Constraints:
  promote pgsqld-clone then start ip-virtual (kind:Mandatory) (non-symmetrical) (id:order-pgsqld-clone-ip-virtual-Mandatory)
  demote pgsqld-clone then stop ip-virtual (kind:Mandatory) (non-symmetrical) (id:order-pgsqld-clone-ip-virtual-Mandatory-1)
Colocation Constraints:
  ip-virtual with pgsqld-clone (score:INFINITY) (rsc-role:Started) (with-rsc-role:Master) (id:colocation-ip-virtual-pgsqld-clone-INFINITY)
Ticket Constraints:

Alerts:
 No alerts defined

Resources Defaults:
 migration-threshold=5
 resource-stickiness=100
Operations Defaults:
 No defaults set

Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: pg_cluster
 dc-version: 2.1.1-alt1-77db57872
 have-watchdog: false
 no-quorum-policy: ignore
 stonith-enabled: false

Quorum:
  Options:

Статус кластера в консоли:
pcs status --full
Cluster name: pg_cluster
Cluster Summary:
  * Stack: corosync
  * Current DC: linux-db1 (1) (version 2.1.1-alt1-77db57872) - partition with quorum
  * Last updated: Fri Dec 10 11:00:01 2021
  * Last change:  Fri Dec 10 10:28:02 2021 by root via crm_attribute on linux-db1
  * 2 nodes configured
  * 3 resource instances configured

Node List:
  * Online: [ linux-db1 (1) linux-db2 (2) ]

Full List of Resources:
  * Clone Set: pgsqld-clone [pgsqld] (promotable):
    * pgsqld    (ocf:heartbeat:pgsqlms):         Promoted linux-db1
    * pgsqld    (ocf:heartbeat:pgsqlms):         Unpromoted linux-db2
  * ip-virtual  (ocf:heartbeat:IPaddr2):         Started linux-db1

Node Attributes:
  * Node: linux-db1 (1):
    * master-pgsqld                     : 1001
  * Node: linux-db2 (2):
    * master-pgsqld                     : 1000

Migration Summary:

Tickets:

PCSD Status:
  linux-db1: Online
  linux-db2: Online

Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/enabled

Прикладываю скриншот с вебой. Странно что в консоли пишет, что linux-db1 promoted, т.е. продвинут. А веба пишет о том, что нет продвинутых.
Заранее благодарю за помощь.