29.3. Removing a Booth ticket

Procedure

1. From a cluster node in one cluster site of the Booth configuration:

   1. Put the ticket to remove in standby mode. The ticket that this example uses is named apacheticket.

      [cluster1-node1 ~]# pcs booth ticket standby apacheticket

   2. Remove the ticket from the Booth configuration.

      [cluster1-node1 ~]# pcs booth ticket remove apacheticket

   3. Synchronize the Booth configuration to all nodes in the current cluster.

      [cluster1-node1 ~]# pcs booth sync

   4. Restart the Booth resource in the current cluster.

      [cluster1-node1 ~]# pcs booth restart

   5. Remove the ticket from the CIB in the current cluster.

      [cluster1-node1 ~]# pcs booth ticket cleanup

2. From a cluster node in each remaining cluster site of the Booth configuration:

   1. Put the ticket to remove in standby mode.

      [cluster2-node1 ~]# pcs booth ticket standby apacheticket

   2. Download the Booth configuration file from a node with the updated configuration.

      [cluster2-node1 ~]# pcs booth pull cluster1-node1

   3. Synchronize the Booth configuration to all nodes in the current cluster.

      [cluster2-node1 ~]# pcs booth sync

   4. Restart the Booth resource in the current cluster.

      [cluster2-node1 ~]# pcs booth restart

   5. Remove the ticket from the CIB in the current cluster.

      [cluster2-node1 ~]# pcs booth ticket cleanup

3. From the arbitrator node, download the updated Booth configuration file from a node with the updated configuration:

   [arbitrator-node ~]# pcs booth pull clusternode-node1

Verification

1. To check whether a Booth ticket was removed from the Booth configuration, run the pcs booth config command on each cluster node and the arbitratror node.

   For example, after configuring a ticket named apacheticket using the procedure described in Configuring multi-site clusters with Pacemaker, the command displays the following output:

   [cluster1-node1 ~]# pcs booth config
   authfile = /etc/booth/booth.key/
   site = 192.168.11.100
   site = 192.168.22.100
   arbitrator = 192.168.99.100
   ticket = "apacheticket"

   After you remove the ticket from the Booth configuration, the command no longer displays ticket= "apacheticket":

   [cluster1-node1 ~]# pcs booth config
   authfile = /etc/booth/booth.key
   site = 192.168.11.100
   site = 192.168.22.100
   arbitrator = 192.168.99.100

2. To check whether a Booth ticket was removed from the CIB on a cluster node, use the --query-xml option of the crm_ticket utility on any node in the cluster. For example, after you have configured a Booth ticket named apacheticket, the utility displays the following output:

   [cluster1-node1 ~]# crm_ticket --query-xml
   State XML:
   
   <tickets>
     <ticket_state id="apacheticket" granted="true" booth-cfg-name="booth" owner="0" expires="1740986835" term="0" standby="false"/>
   </tickets>

   After you have removed the ticket from the CIB, the output no longer displays a ticket_state element with id="apacheticket":

   [cluster1-node1 ~]# crm_ticket --query-xml
   State XML:
   
   <tickets/>