Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-69040

[RFE] Add commands for ticket standby, activate and cleanup [rhel-9]

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • rhel-9.6
    • rhel-9.0.0
    • pcs
    • pcs-0.11.8-3.el9
    • None
    • FutureFeature
    • rhel-sst-high-availability
    • 17
    • 23
    • 2
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Enhancement
    • Hide
      .Removing Booth cluster tickets from the CIB after removal from the Booth configuration

      After you remove a Booth cluster ticket with the `pcs booth ticket remove` command, or after you pull a Booth configuration to another site with the `pcs booth pull` command, the state of the Booth ticket remains loaded in the Cluster Information Base (CIB). This can cause issues when you configure a ticket constraint, since a ticket constraint can be granted even after a ticket has been removed and the cluster may freeze or fence a node. To prevent this, you can now remove a Booth ticket from the CIB with the new `pcs booth ticket cleanup` command.

      Perform the following steps to remove a Booth ticket when Booth is in use:

      . Put the ticket in standby mode by using the new `pcs booth ticket standby` command.
      . Remove the ticket by using the `pcs booth ticket remove` command.
      . Restart Booth by using the `pcs booth restart` command.
      . Remove the ticket from the CIB by using the new `pcs booth ticket cleanup` command. You must specify the ticket to remove.
          
      Perform the following steps to remove a Booth ticket when tickets are managed manually and Booth is not in use:

      . Put the ticket in standby mode by using the new `pcs booth ticket standby` command.
      . Remove the ticket from the CIB by using the new `pcs booth ticket cleanup` command. You must specify the ticket to remove.

      Show
      .Removing Booth cluster tickets from the CIB after removal from the Booth configuration After you remove a Booth cluster ticket with the `pcs booth ticket remove` command, or after you pull a Booth configuration to another site with the `pcs booth pull` command, the state of the Booth ticket remains loaded in the Cluster Information Base (CIB). This can cause issues when you configure a ticket constraint, since a ticket constraint can be granted even after a ticket has been removed and the cluster may freeze or fence a node. To prevent this, you can now remove a Booth ticket from the CIB with the new `pcs booth ticket cleanup` command. Perform the following steps to remove a Booth ticket when Booth is in use: . Put the ticket in standby mode by using the new `pcs booth ticket standby` command. . Remove the ticket by using the `pcs booth ticket remove` command. . Restart Booth by using the `pcs booth restart` command. . Remove the ticket from the CIB by using the new `pcs booth ticket cleanup` command. You must specify the ticket to remove.      Perform the following steps to remove a Booth ticket when tickets are managed manually and Booth is not in use: . Put the ticket in standby mode by using the new `pcs booth ticket standby` command. . Remove the ticket from the CIB by using the new `pcs booth ticket cleanup` command. You must specify the ticket to remove.
    • Proposed
    • None

      This is a clone of issue RHEL-12709 to use for version rhel-9.6
      –
      Original description:
      When removing a booth ticket with pcs booth ticket remove, the ticket is only removed from booth config file and is still present in CIB. We need to provide additional commands for managing tickets and expanse the documentation to describe the proper ticket removal process. There is a catch when removing tickets: based on ticket-loss policy configured in a ticket constraint, the cluster may freeze or fence on a ticket removal. This is not something one would except to be an outcome of merely updating cluster configuration.

      Proper ticket removal process when booth is in use:

      • standby a ticket
      • remove the ticket from booth + restart booth
      • remove the ticket from cib (cleanup) - this step may become unnecessary once booth is updated to autoremove tickets from cib on restart

      Proper ticket removal process when booth is not in use - i.e. tickets are managed manually:

      • standby a ticket
      • remove the ticket from cib (cleanup)

      Pcs doesn't currently provide commands to standby and cleanup tickets, so we need to add them. We should also add a command to unstandby tickets to offer a complete set of commands. Documentation of ticket remove, standby and cleanup commands should describe effects of these commands and proper ticket removal procedure in detail.

              mnovacek@redhat.com Michal Nováček
              watson-automation Watson Automation
              Peter Romancik Peter Romancik
              Michal Nováček Michal Nováček
              Steven Levine Steven Levine
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: