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

Improve documentation and error messages of `pcs resource move` command

XMLWordPrintable

    • pcs-0.10.17-5.el8
    • None
    • Moderate
    • rhel-sst-high-availability
    • ssg_filesystems_storage_and_HA
    • 13
    • 19
    • 2
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • Release Note Not Required
    • Hide
      Feature:
      Improve an error message when 'pcs resource move' command fails.

      Reason:
      Previously, it wasn't clear in which phase the command failed and what it left behind in the cluster configuration.

      Result:
      If the command left a move constraint behind, pcs explicitly points it out and provides a guidance on removing the constraint.
      Show
      Feature: Improve an error message when 'pcs resource move' command fails. Reason: Previously, it wasn't clear in which phase the command failed and what it left behind in the cluster configuration. Result: If the command left a move constraint behind, pcs explicitly points it out and provides a guidance on removing the constraint.
    • None

      +++ This bug was initially created as a clone of Bug #2219554 +++

      Documentation of `pcs resource move` command needs to better describe a case when command fails and a constraint used to move the resource is not removed by pcs afterwards. Error message produced by pcs in a such case may also be improved to suggest to use `pcs resource clear <resource> [<node>]` command in order to remove the constraint. However, the error message should be clear that removal of the constraint may cause the resource to move to another node.

        1. rhel-7742-constraints.patch
          0.6 kB

              cluster-qe Cluster QE
              tojeline@redhat.com Tomas Jelinek
              Tomas Jelinek Tomas Jelinek
              Nina Hostakova Nina Hostakova
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: