No more than one gcp-vpc-move-vip resource can run on a node at a particular time in a Pacemaker cluster

Issue

• When a second gcp-vpc-move-vip resource starts on a node where a gcp-vpc-move-vip resource is already running, the two resources repeatedly fail their monitor operations and restart.

Jun 13 08:06:10 node2 crmd[1601]:  notice: Result of start operation for alias_ip2 on node2: 0 (ok)
...
Jun 13 08:06:46 node2 pengine[1600]: warning: Processing failed monitor of alias_ip1 on node2: not running
Jun 13 08:06:46 node2 pengine[1600]:  notice:  * Recover    alias_ip1     (                      node2 )
Jun 13 08:06:46 node2 crmd[1601]:  notice: Initiating stop operation alias_ip1_stop_0 locally on node2
Jun 13 08:06:47 node2 crmd[1601]:  notice: Initiating start operation alias_ip1_start_0 locally on node2
Jun 13 08:06:47 node2 gcp-vpc-move-vip: INFO: Removing 10.138.0.31/32 from node2
Jun 13 08:06:49 node2 GCEGuestAgent[920]: 2020-06-13T08:06:49.5091Z GCEGuestAgent Info: Changing forwarded IPs for 42:01:0a:8a:00:03 from ["10.138.0.31"] to [] by removing ["10.138.0.31"]
Jun 13 08:06:57 node2 GCEGuestAgent[920]: 2020-06-13T08:06:57.9045Z GCEGuestAgent Info: Changing forwarded IPs for 42:01:0a:8a:00:03 from [] to ["10.138.0.30"] by adding ["10.138.0.30"]
Jun 13 08:07:00 node2 gcp-vpc-move-vip: INFO: Finished adding 10.138.0.30/32 to node2
Jun 13 08:07:00 node2 crmd[1601]:  notice: Result of start operation for alias_ip1 on node2: 0 (ok)
...
Jun 13 08:07:11 node2 pengine[1600]: warning: Processing failed monitor of alias_ip2 on node2: not running
Jun 13 08:07:11 node2 pengine[1600]:  notice:  * Recover    alias_ip2     (                      node2 )
Jun 13 08:07:11 node2 crmd[1601]:  notice: Initiating stop operation alias_ip2_stop_0 locally on node2
...
Jun 13 08:07:11 node2 crmd[1601]:  notice: Initiating start operation alias_ip2_start_0 locally on node2