How to show Pacemaker resource configuration

Reviewing a Pacemaker resource definition confirms which agent, parameters, and monitoring rules the cluster enforces, which helps catch surprises before they trigger unwanted restarts or failovers.

In a Pacemaker cluster managed with pcs, resources are stored in the cluster information base (CIB) as primitives and higher-level objects such as groups or clones. The pcs resource config command renders that stored definition, showing the resource agent (class/provider/type), instance attributes, meta-attributes, and configured operations such as monitor intervals.

Configuration output describes intended behavior rather than current placement or health, and placement rules may also be controlled by separate constraint objects. Run the command on a node with cluster connectivity and sudo privileges, and treat any printed credentials or sensitive paths as change-control artifacts.

1. Open a terminal on a cluster node with sudo privileges.

   $ whoami
   root

2. Display the configuration for a resource.

   $ sudo pcs resource config web-service
   Resource: web-service (class=systemd type=nginx)
     Operations:
       monitor: web-service-monitor-interval-30s
         interval=30s
       start: web-service-start-interval-0s
         interval=0s timeout=100
       stop: web-service-stop-interval-0s
         interval=0s timeout=100

   Check Class and Type to confirm the intended resource agent, and review Operations to confirm monitor intervals match the expected policy.

3. Show the full resource list for context.

   $ sudo pcs resource config
   Resource: cluster_ip (class=ocf provider=heartbeat type=IPaddr2)
     Attributes: cluster_ip-instance_attributes
       cidr_netmask=24
       ip=192.0.2.40
     Operations:
       monitor: cluster_ip-monitor-interval-30s
         interval=30s
       start: cluster_ip-start-interval-0s
         interval=0s timeout=20s
       stop: cluster_ip-stop-interval-0s
         interval=0s timeout=20s
   Resource: web-service (class=systemd type=nginx)
     Operations:
       monitor: web-service-monitor-interval-30s
         interval=30s
       start: web-service-start-interval-0s
         interval=0s timeout=100
       stop: web-service-stop-interval-0s
         interval=0s timeout=100

   Large clusters can produce long output. Extract the resource name from this list and rerun pcs resource config <name> for a focused definition.