Bug 2111583
| Summary: | Warning about existing constraints in 'pcs status' should not display expired constraints | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Nina Hostakova <nhostako> | |
| Component: | pcs | Assignee: | Peter Romancik <promanci> | |
| Status: | CLOSED MIGRATED | QA Contact: | cluster-qe <cluster-qe> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 8.7 | CC: | cluster-maint, idevat, mlisik, mpospisi, omular, tojeline | |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged | |
| Target Release: | 8.10 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2111591 (view as bug list) | Environment: | ||
| Last Closed: | 2023-09-22 19:50:23 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 2111591 | |||
| Bug Blocks: | ||||
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 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. 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. |
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