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

Fix inconsistent approach for multiple `attributes.attrs` in `ha_cluster_node_options`

XMLWordPrintable

    • rhel-system-roles-1.78.1-0.1.el9
    • None
    • Moderate
    • 4
    • sst_system_roles
    • 13
    • 3
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • System Roles Sprint 1, System Roles Sprint 2, System Roles Sprint 3, System Roles Sprint 4
    • Bug Fix
    • Hide
      .Implementation of multiple sets of key-value pairs of node attributes is now consistent with other cluster configuration components

      The `ha_cluster` RHEL system role supports only one set of key-value pairs for each configuration item. Previously, when you configured multiple sets of node attributes, the sets were merged into a single set. With this update, the role uses only the first set you define and ignores the other sets. This behavior is now consistent with how the role implements multiple sets of key-value pairs for other configuration components that use a key-value pair structure.
      Show
      .Implementation of multiple sets of key-value pairs of node attributes is now consistent with other cluster configuration components The `ha_cluster` RHEL system role supports only one set of key-value pairs for each configuration item. Previously, when you configured multiple sets of node attributes, the sets were merged into a single set. With this update, the role uses only the first set you define and ignores the other sets. This behavior is now consistent with how the role implements multiple sets of key-value pairs for other configuration components that use a key-value pair structure.
    • Done
    • None

      In HA Cluster configuration, there is a common structure that allows multiple sets of key-value pairs. However, `pcs`, which is used by the `system_role_ha_cluster` for creating configuration, does support only a single set of the key-value pairs.

      In the `system_role_ha_cluster` appeared two different approaches to deal with it:

      • use only the first set and ignore the rest (in the most cases)
      • merge multiple sets into one single set (in the case of `ha_cluster_node_options.attributes.attrs`)

      Such inconsistency can confuse a user and may complicate the possible future addition of support for multiple sets. So, node attributes should be modified to behave like the other cases. Also in README should be the behavior explicitly mentioned.

              rmeggins@redhat.com Richard Megginson
              idevat@redhat.com Ivan Devát
              Ivan Devát Ivan Devát
              David Jez David Jez
              Steven Levine Steven Levine
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: