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

crm_mon -1 sometimes report only part information

XMLWordPrintable

    • pacemaker-2.1.7-1.el8
    • None
    • Low
    • rhel-sst-high-availability
    • ssg_filesystems_storage_and_HA
    • 13
    • 22
    • 5
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Bug Fix
    • Hide
      Cause: When a node joined the cluster, Pacemaker previously erased its known resource history and updated it with the current known status in two separate steps.

      Consequence: If "pcs status" were run between the two steps, it would wrongly appear that no resources were active on the joining node.

      Fix: The erase and update are now done in a single CIB modification.

      Result: "pcs status" always shows the correct known state
      Show
      Cause: When a node joined the cluster, Pacemaker previously erased its known resource history and updated it with the current known status in two separate steps. Consequence: If "pcs status" were run between the two steps, it would wrongly appear that no resources were active on the joining node. Fix: The erase and update are now done in a single CIB modification. Result: "pcs status" always shows the correct known state
    • All
    • 2.1.7
    • None

      Description of problem:
      I have scripts which use 'crm_non -1'. and sometimes the script failed. after debugging I found sometimes 'crm_mon -1' didn't report full information

      Version-Release number of selected component (if applicable):
      pacemaker-cli-2.1.0-8.el8.x86_64

      How reproducible:
      sometimes

      Steps to Reproduce:
      1. do some change to cluster configuration
      2. run 'crm_mon -1' to get the cluster status
      3.

      Actual results:
      sometimes the report is not full, only part of information

      Expected results:
      full correct information

      Additional info:
      I notice when the report time of "Last updated:" and "Last change:" are the same or very close, then it may trigger the problem.

      please check attachment which shows the "good" and "bad" report.

              rh-ee-jrehova Jana Rehova
              jira-bugzilla-migration RH Bugzilla Integration
              Reid Wahl Reid Wahl
              Jana Rehova Jana Rehova
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: