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

`pcs dr status` fails with Unknown command 'status.full_cluster_status_plaintext' [rhel-9]

    • pcs-0.11.8-2.el9
    • Yes
    • Moderate
    • ZStream
    • 3b43471a104356b3d696a4f63c205f305997a8ad
    • rhel-sst-high-availability
    • 13
    • 26
    • 1
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • None
    • Approved Blocker
    • Bug Fix
    • Hide
      .Cluster status of a disaster recovery site now displays correctly

      Before this update, when you configured a disaster recovery recovery site and ran the `pcs dr status` command to display the status of the local and remote cluster sites, the command displayed an error instead of the cluster status. With this update, the cluster status of the local and remote sites displays correctly when you execute this command.
      Show
      .Cluster status of a disaster recovery site now displays correctly Before this update, when you configured a disaster recovery recovery site and ran the `pcs dr status` command to display the status of the local and remote cluster sites, the command displayed an error instead of the cluster status. With this update, the cluster status of the local and remote sites displays correctly when you execute this command.
    • Done
    • Unspecified
    • None

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

      Check the status of the primary cluster and the disaster recovery cluster from a node in the primary cluster, after a fresh installation following Red Hat official documentation:

      RHEL 9 - Configuring and managing high availability clusters - Chapter 32. Configuring disaster recovery clusters - 32.2. Displaying status of recovery clusters

      What is the impact of this issue to you?

      Customers can't create a disaster recovery cluster to be managed and monitor using the `pcs` cli from the primary site.

      Please provide the package NVR for which the bug is seen:

      pcs-0.11.7-2.el9_4.1.x86_64

      How reproducible is this bug?:

      Always.

      Steps to reproduce

      1. pcs host auth fastvm-rhel-9-4-21 fastvm-rhel-9-4-22 fastvm-rhel-9-4-23 fastvm-rhel-9-4-24
      1. pcs cluster setup PrimarySite fastvm-rhel-9-4-21 fastvm-rhel-9-4-22 --start
      1. pcs cluster setup DRSite fastvm-rhel-9-4-23 fastvm-rhel-9-4-24 --start
      1. pcs dr set-recovery-site fastvm-rhel-9-4-23
      1. pcs dr status

      Expected results

      An output similar to what we have in our official documentation (see link above); a combined output of `pcs status` as it was executed on each of the sites separately.

      Actual results

      [root@fastvm-rhel-9-4-21 ~]# pcs dr status
      Error: fastvm-rhel-9-4-21: Unknown command 'status.full_cluster_status_plaintext'
      Error: fastvm-rhel-9-4-22: Unknown command 'status.full_cluster_status_plaintext'
      Error: fastvm-rhel-9-4-23: Unknown command 'status.full_cluster_status_plaintext'
      Error: fastvm-rhel-9-4-24: Unknown command 'status.full_cluster_status_plaintext'
      — Local cluster - Primary site —
      Error: Unable to get status of the cluster from any node

      — Remote cluster - Recovery site —
      Error: Unable to get status of the cluster from any node
      Error: Unable to get status of all sites

              mmazoure Michal Mazourek
              rhn-support-jserrano Jesús Serrano Sánchez-Toscano
              Miroslav Lisik Miroslav Lisik
              Michal Mazourek Michal Mazourek
              Steven Levine Steven Levine
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: