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

Warning about existing constraints in 'pcs status' should not display expired constraints

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • rhel-9.4
    • rhel-9.1.0
    • pcs
    • pcs-0.11.6-6.el9
    • sst_high_availability
    • ssg_filesystems_storage_and_HA
    • 13
    • 19
    • 2
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      .Output of `pcs status` command no longer shows warning for expired constraints

      Previously, when moving a cluster resource created a temporary location constraint, the `pcs status` command displayed a warning even after the constraint expired. With this fix, the `pcs status` command filters out expired constraints and they no longer generate a warning message in the command output.
      Show
      .Output of `pcs status` command no longer shows warning for expired constraints Previously, when moving a cluster resource created a temporary location constraint, the `pcs status` command displayed a warning even after the constraint expired. With this fix, the `pcs status` command filters out expired constraints and they no longer generate a warning message in the command output.
    • Done
    • None

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

      Description of problem:
      The new feature of pcs prints out a warning when location constraints are created by moving resources. The warning about existing constraints is displayed in 'pcs status' as well. This warning should not be present in status when the constraint is no longer in effect, i.e. temporary constraints created with --lifetime parameter that are already expired.

      Version-Release number of selected component (if applicable):
      pcs-0.10.14-1.el8.x86_64

      How reproducible:
      always

      Steps to Reproduce:

      1. pcs resource move dummy1 lifetime=PT1M
        Migration will take effect until: 2022-07-20 15:13:12 +02:00
        Warning: Creating location constraint 'cli-ban-dummy1-on-virt-487' with a score of -INFINITY for resource dummy1 on virt-487.
        This will prevent dummy1 from running on virt-487 until the constraint is removed
        This will be the case even if virt-487 is the last node in the cluster
      1. date
        Wed Jul 20 15:12:17 CEST 2022
      1. pcs constraint location
        Location Constraints:
        Resource: dummy1
        Constraint: cli-ban-dummy1-on-virt-487
        Rule: boolean-op=and score=-INFINITY
        Expression: #uname eq string virt-487
        Expression: date lt 2022-07-20 15:13:12 +02:00
      1. pcs status | grep "WARNINGS" -A 3
        WARNINGS:
        Following resources have been moved and their move constraints are still in place: 'dummy1'
        Run 'pcs constraint location' or 'pcs resource clear <resource id>' to view or remove the constraints, respectively
      1. date
        Wed Jul 20 15:13:22 CEST 2022
      1. pcs constraint location
        Location Constraints:
      1. pcs status | grep "WARNINGS" -A 3
        WARNINGS:
        Following resources have been moved and their move constraints are still in place: 'dummy1'
        Run 'pcs constraint location' or 'pcs resource clear <resource id>' to view or remove the constraints, respectively

      Additional info:
      Introduced in RFE bz1730232

            cluster-qe Cluster QE
            rhn-support-nhostako Nina Hostakova
            Peter Romancik Peter Romancik
            Nina Hostakova Nina Hostakova
            Steven Levine Steven Levine
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: