This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2111583 - Warning about existing constraints in 'pcs status' should not display expired constraints
Summary: Warning about existing constraints in 'pcs status' should not display expired...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.10
Assignee: Peter Romancik
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On: 2111591
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-27 14:43 UTC by Nina Hostakova
Modified: 2023-09-22 19:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Temporary location constraint is created by moving the resources Consequence: Warning in `pcs status` command is shown despite the location constraint being already expired Fix: Filter out expired constraints when displaying warning in the `pcs status` command Result: Warning in `pcs status` is not displayed for location constraints that are already expired
Clone Of:
: 2111591 (view as bug list)
Environment:
Last Closed: 2023-09-22 19:50:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7668 0 None Migrated None 2023-09-22 19:50:30 UTC
Red Hat Issue Tracker RHELPLAN-129304 0 None None None 2022-07-27 14:46:08 UTC

Description Nina Hostakova 2022-07-27 14:43:10 UTC 
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:

# 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

# date
Wed Jul 20 15:12:17 CEST 2022

# 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

# 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

# date
Wed Jul 20 15:13:22 CEST 2022

# pcs constraint location
Location Constraints:

# 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
Comment 2 Peter Romancik 2023-09-14 07:36:59 UTC 
Upstream commit: https://github.com/ClusterLabs/pcs/commit/de41961e8c3d10ca99eecf16b8c874426a135830

Environment: A running cluster with resource

# pcs resource move dummy1 lifetime=PT1M
Migration will take effect until: 2023-09-14 08:47:01 +02:00
Warning: Creating location constraint 'cli-ban-dummy1-on-r92-2' with a score of -INFINITY for resource dummy1 on r92-2.
	This will prevent dummy1 from running on r92-2 until the constraint is removed
	This will be the case even if r92-2 is the last node in the cluster

# date
Thu Sep 14 08:46:06 AM CEST 2023

# pcs constraint location
Location Constraints:
  Started resource 'dummy1'
    Rules:
      Rule: boolean-op=and score=-INFINITY
        Expression: #uname eq string r92-2
        Expression: date lt 2023-09-14T08:47:01+02:00

# 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

# date
Thu Sep 14 08:49:14 AM CEST 2023

# pcs constraint location
Location Constraints:

# pcs status | grep "WARNINGS" -A 3 | wc -l
0
Comment 3 RHEL Program Management 2023-09-22 19:48:00 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4 RHEL Program Management 2023-09-22 19:50:23 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.