Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 12. High availability and clusters

The following chapter contains the most notable changes to high availability and clusters between RHEL 9 and RHEL 10.

Support for the RHEL Resilient Storage Add-On has been removed

The Red Hat Enterprise Linux (RHEL) Resilient Storage Add-On will no longer be supported starting with Red Hat Enterprise Linux 10 and any subsequent releases after RHEL 10. The RHEL Resilient Storage Add-On will continue to be supported with earlier versions of RHEL (7, 8, 9) and throughout their respective maintenance support lifecycles.

pcsd Web UI no longer available as a standalone user interface

The pcsd Web UI is now available as the HA Cluster Management RHEL web console add-on when the cockpit-ha-cluster package is installed. It is no longer operated as a standalone interface.

Removed functionality for the Red Hat High Availability Add-On

The following Red Hat High Availability Add-On features are no longer supported in RHEL 10.

  • RKT containers in bundles. Docker and Podman containers are still supported.
  • The upstart and nagios resource classes.
  • Location constraints with multiple top-level rules. Only one rule per constraint is allowed. The pcs constraint rule add, pcs constraint rule delete and the pcs constraint rule remove commands have been removed. If you have configured constraints with multiple rules, run the pcs cluster cib-upgrade command to update to the latest CIB schema. During the update, Pacemaker creates a constraint for each rule, so that there will be only one rule in each constraint.
  • The monthdays, moon, weekdays, weekyears, and yearsdays duration options for Pacemaker rules.
  • Using spaces in dates in location constraint rules.
  • Delimiting stonith devices with a comma in pcs stonith level add | clear | delete | remove commands.
  • Ambiguous syntax of the pcs stonith level clear | delete | remove command. The commnd has been clarified to distinguish a target from a stonith device.
  • The legacy role names of master and slave are no longer accepted by the pcs command-line interface. Use Promoted, Unpromoted, --promoted, promotable, and promoted-max instead.
  • Using stonith resources in pcs resource commands and resources in pcs stonith commands, as well as --brief, --no-strict,--safe and --simulate flags of the pcs stonith disable command
  • Ability to create a stonith resource in a group with the pcs stonith create command
  • The stonith.create_in_group command from API v1 and v2
  • The pcs cluster pcsd-status command. Use the pcs status pcsd or pcs pcsd status command.
  • The pcs cluster certkey command. Use the pcs pcsd certkey command.
  • The pcs resource | stonith [op] defaults <name>=<value>…​ command. Use the pcs resource | stonith [op] defaults update command.
  • The pcs acl show command. Use the pcs acl config command.
  • The pcs alert show command. Use the pcs alert config command.
  • The pcs constraint [location | colocation | order | ticket] show | list commands. Use the pcs constraint [location | colocation | order | ticket] config command.
  • The pcs property show and the pcs property list commands. Use the pcs property config command.
  • The pcs tag list command. Use the pcs tag config command.
  • The --autodelete flag of the pcs resource move command.

Removed and updated Pacemaker CIB elements

The following configuration components of the Pacemaker CIB have been removed or modified in RHEL 10. When you upgrade to RHEL 10, these components are automatically removed, modified, or replaced as described. Before you upgrade, ensure that the Pacemaker CIB has a supported value for the validate-with attribute. Although you should not edit the cluster configuration file directly, you can view the raw cluster configuration with the pcs cluster cib command.

An upgrade modifies the following CIB components:

  • The validate-with attribute of the cib element, which is set to pacemaker-4.0
  • The stonith-action cluster property, which is set to off if it was previously set to poweroff
  • Legacy promotable clone (master) resources, which are changed to standard promotable clones by changing the master xml element to the clone xml element and by setting the promotable meta attribute
  • Location constraints with more than one top-level rule, which are converted to separate location constraints for each top-level rule

An upgrade renames the following components:

  • The crmd-finalization-timeout cluster property, which is renamed to join-finalization-timeout
  • The crmd-integration-timeout cluster property, which is renamed to join-integration-timeout
  • The crmd-transition-delay cluster property, which is renamed to transition-delay

An upgrade removes the following components from the CIB:

  • nagios-class and upstart-class resources
  • bundle resources based on an rkt container.
  • The restart-type resource meta-attribute
  • The can_fail operation meta-attribute
  • The role_after_failure operation meta-attribute
  • moon attributes in date_spec elements of rules
  • The remove-after-stop cluster property.
  • Ping nodes, which are changed to cluster member nodes with all resources banned and probes disabled
  • NVpairs without a value attribute
  • Duplicate NVpairs with a given name within an NVset, for which only the first NVpair is kept

An upgrade changes the following default values:

  • An action configured as a fence device parameter is now ignored rather than treated as a default fencing action.
  • The concurrent-fencing cluster option now defaults to true and is deprecated.
  • The globally-unique clone option now defaults to true when clone-node-max is greater than 1.

An upgrade removes lifetime elements, and modifies the CIB as follows:

  • lifetime elements in a location constraint are removed.

    • If the lifetime element in a location constraint has no top-level rules, the lifetime-based rule becomes the constraint’s top-level rule.
    • If the lifetime element in a location constraint has multiple top-level rules, they are nested inside a single or rule.
    • If the lifetime element in a location constraint has a single top-level rule, a new and top-level constraint rule is added that contains the existing top-level constraint rule and the lifetime-based rule.
  • lifetime elements in a colocation or order constraint are removed. If any rules contained in the colocation or order constraint are referenced elsewhere, they are put in a new location constraint that does not apply to any resources. They are put in a location constraint since a rule in a lifetime element may contain a node attribute expression, which is now allowed only within a location constraint rule.
  • Following an upgrade, invalid fencing levels display a warning when the CIB is loaded.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat