crm_ticket - Man Page

Part of the Pacemaker cluster resource manager

Synopsis

crm_ticket <query>|<command> [options]

Description

crm_ticket - perform tasks related to cluster tickets

Allows ticket attributes to be queried, modified and deleted.

Options

-?,  --help

This text

-$,  --version

Version information

-V,  --verbose

Increase debug output

-Q,  --quiet

Print only the value on stdout

-t,  --ticket=value

Ticket ID

Queries

-l,  --info

Display the information of ticket(s)

-L,  --details

Display the details of ticket(s)

-w,  --raw

Display the IDs of ticket(s)

-q,  --query-xml

Query the XML of ticket(s)

-c,  --constraints

Display the rsc_ticket constraints that apply to ticket(s)

Commands

-g,  --grant

Grant a ticket to this cluster site

-r,  --revoke

Revoke a ticket from this cluster site

-s,  --standby

Tell this cluster site this ticket is standby

-a,  --activate

Tell this cluster site this ticket is active

Advanced Commands

-G,  --get-attr=value

Display the named attribute for a ticket

-S,  --set-attr=value

Set the named attribute for a ticket

-D,  --delete-attr=value

Delete the named attribute for a ticket

-C,  --cleanup

Delete all state of a ticket at this cluster site

Additional Options

-v,  --attr-value=value

Attribute value to use with -S

-d,  --default=value

(Advanced) Default attribute value to display if none is found (for use with -G)

-f,  --force

(Advanced) Force the action to be performed

-n,  --set-name=value

(Advanced) ID of the instance_attributes object to change

-i,  --nvpair=value

(Advanced) ID of the nvpair object to change/delete

Examples

Display the info of tickets:

# crm_ticket --info

Display the detailed info of tickets:

# crm_ticket --details

Display the XML of 'ticketA':

# crm_ticket --ticket ticketA --query-xml

Display the rsc_ticket constraints that apply to 'ticketA':

# crm_ticket --ticket ticketA --constraints

Grant 'ticketA' to this cluster site:

# crm_ticket --ticket ticketA --grant

Revoke 'ticketA' from this cluster site:

# crm_ticket --ticket ticketA --revoke

Make 'ticketA' standby (the cluster site will treat a granted 'ticketA' as 'standby', and the dependent resources will be stopped or demoted gracefully without triggering loss-policies):

# crm_ticket --ticket ticketA --standby

Activate 'ticketA' from being standby:

# crm_ticket --ticket ticketA --activate

Get the value of the 'granted' attribute for 'ticketA':

# crm_ticket --ticket ticketA --get-attr granted

Set the value of the 'standby' attribute for 'ticketA':

# crm_ticket --ticket ticketA --set-attr standby --attr-value true

Delete the 'granted' attribute for 'ticketA':

# crm_ticket --ticket ticketA --delete-attr granted

Erase the operation history of 'ticketA' at this cluster site:

The cluster site will 'forget' the existing ticket state.

# crm_ticket --ticket ticketA --cleanup

Author

Written by Andrew Beekhof

Reporting Bugs

Report bugs to users@clusterlabs.org

Referenced By

geostore(8).

March 2021 Pacemaker 2.0.5-10.fc35.2 System Administration Utilities