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

crm_node mishandles node IDs [rhel-8.10.z]

XMLWordPrintable

    • pacemaker-2.1.7-5.2.el8_10
    • Yes
    • None
    • ZStream, Regression
    • rhel-sst-high-availability
    • ssg_filesystems_storage_and_HA
    • 21
    • 26
    • 2
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • None
    • Approved Blocker
    • Bug Fix
    • Hide
      Cause (the user action or circumstances that trigger the bug): The crm_node command mishandles node IDs when called with the dash i / dashdash cluster-id argument.

      Consequence (what the user experience is when the bug occurs): crm_node dash i / dashdash cluster-id, which is supposed to show the local node's cluster ID, sometimes shows "Node is not known to cluster" instead.

      Fix (what has changed to fix the bug; do not include overly technical details): Node IDs are now properly parsed.

      Result (what happens now that the patch is applied): The command works as intended.
      Show
      Cause (the user action or circumstances that trigger the bug): The crm_node command mishandles node IDs when called with the dash i / dashdash cluster-id argument. Consequence (what the user experience is when the bug occurs): crm_node dash i / dashdash cluster-id, which is supposed to show the local node's cluster ID, sometimes shows "Node is not known to cluster" instead. Fix (what has changed to fix the bug; do not include overly technical details): Node IDs are now properly parsed. Result (what happens now that the patch is applied): The command works as intended.
    • Proposed
    • All
    • None

      What were you trying to do that didn't work?

      Since upstream version 2.1.7 (RHEL 8.10 / 9.4), crm_node dash i / dashdash cluster-id, which is supposed to show the local node's cluster ID, can show "Node is not known to cluster" instead.

      Steps to reproduce

      1. Run crm_node -i repeatedly

      Expected results

      crm_node -i always gives the local node ID

      Actual results

      crm_node -i sometimes gives an error

      Other notes

      I (Reid) could reproduce this on Fedora 39 only after installing the pacemaker-2.1.7-5.fc39.x86_64 package from the fedora repo via dnf. When I built and installed from source, the uninitialized local variable that causes the problem was always set to 0 by gcc.

              mjuricek@redhat.com Martin Juricek
              kgaillot@redhat.com Kenneth Gaillot
              Christopher Lumens Christopher Lumens
              Martin Juricek Martin Juricek
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: