[ClusterLabs] unable to start fence_scsi on a new add node

Hi there, i have expanded a cluster with 2 nodes with an additional one "elastic-03". However, fence_scsi does not start on the new node. pcs-status: [root@logger cluster]# pcs status Cluster name: cluster_elastic Stack: corosync Current DC: elastic-02 (version 1.1.20-5.el7_7.2-3c4c782f70) -

Re: [ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump

Hi, My suggestion would be to unmanage the IP resource before putting the node in standby. When a resource is unmanaged, the cluster will not start or stop it. On Thu, 2020-04-16 at 17:57 +0800, 邴洪涛 wrote: > >hi: > > We now get a strange requirement. When the active node enters > standby >

Re: [ClusterLabs] Off-line build-time cluster configuration

Hi Craig, Currently, there is no support in RHEL8 for an equivalent of the --local option of the 'pcs cluster setup' command from RHEL7. We were focusing higher priority tasks related to supporting the new major version of corosync and knet. As a part of this, the 'pcs cluster setup' command

Re: [ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump

On April 16, 2020 12:57:05 PM GMT+03:00, "邴洪涛" <695097494p...@gmail.com> wrote: >>*hi: >*>* We now get a strange requirement. When the active node enters >standby >*>*mode, virtual_ip will not automatically jump to the normal node, but >*>*requires manual operation to achieve the jump of

[ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump

>*hi: *>* We now get a strange requirement. When the active node enters standby *>*mode, virtual_ip will not automatically jump to the normal node, but *>*requires manual operation to achieve the jump of virtual_ip *>* The mode we use is Active / Passive mode *>* The Resource Agent we use

[ClusterLabs] When the active node enters the standby state, what should be done to make the VIP not automatically jump

hi: We now get a strange requirement. When the active node enters standby mode, virtual_ip will not automatically jump to the normal node, but requires manual operation to achieve the jump of virtual_ip The mode we use is Active / Passive mode The Resource Agent we use is ocf: