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 1718386 - let pcs resource clear print out removed constraints
Summary: let pcs resource clear print out removed constraints
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: 8.1
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1631752
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-07 15:36 UTC by Ken Gaillot
Modified: 2020-11-14 12:06 UTC (History)
14 users (show)

Fixed In Version: pcs-0.10.1-6.el8
Doc Type: Enhancement
Doc Text:
Feature: The "pcs resource clear" command should print out removed constraints. Reason: To let the user know which constraints, if any, were removed by it. Result: The "pcs resource clear" command prints output from pacemaker.
Clone Of: 1631752
Environment:
Last Closed: 2019-11-05 20:40:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3311 0 None None None 2019-11-05 20:41:14 UTC

Description Ken Gaillot 2019-06-07 15:36:30 UTC 
This was implemented in pacemaker for 8.1, but it appears pcs is filtering the output. crm_resource --clear shows removed constraints, but pcs resource clear still does not.

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

Description of problem:
When running pcs resource clear, I cannot be sure that anything actually happened. It would be good to print out all actions that have taken place.

Example:
[root@tardis-02 /]# pcs constraint ref gitlab-runner-1
Resource: gitlab-runner-1
  colocation-gitlab-runner-1-libvirtd-clone-INFINITY
  location-gitlab-runner-1-tardis-03-INFINITY
  order-libvirtd-clone-gitlab-runner-1-Mandatory
[root@tardis-02 /]# pcs resource move gitlab-runner-1
Warning: Creating location constraint cli-ban-gitlab-runner-1-on-tardis-03 with a score of -INFINITY for resource gitlab-runner-1 on node tardis-03.
This will prevent gitlab-runner-1 from running on tardis-03 until the constraint is removed. This will be the case even if tardis-03 is the last node in the cluster.
[root@tardis-02 /]# pcs constraint ref gitlab-runner-1
Resource: gitlab-runner-1
  colocation-gitlab-runner-1-libvirtd-clone-INFINITY
  location-gitlab-runner-1-tardis-03-INFINITY
  cli-ban-gitlab-runner-1-on-tardis-03
  order-libvirtd-clone-gitlab-runner-1-Mandatory
[root@tardis-02 /]# pcs resource clear gitlab-runner-1
********************** CHANGE REQUESTED HERE *****************
Removing constraint:   cli-ban-gitlab-runner-1-on-tardis-03
********************** EOR ***********************************
[root@tardis-02 /]# pcs constraint ref gitlab-runner-1
Resource: gitlab-runner-1
  colocation-gitlab-runner-1-libvirtd-clone-INFINITY
  location-gitlab-runner-1-tardis-03-INFINITY
  order-libvirtd-clone-gitlab-runner-1-Mandatory
[root@tardis-02 /]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.5 (Maipo)





Version-Release number of selected component (if applicable):
pcs-0.9.162-5.el7_5.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. see example
2. pcs resource move <resource> && pcs resource clear <resource>
3.

Actual results:
pcs resource clear is silent

Expected results:
pcs resouce clear prints actions it is taking

Additional info:

Pcs merely runs 'crm_resource --resource <resource> --clear' and that does not seem to be providing any output. Ken, are you ok with moving this to pacemaker?

--- Additional comment from Ken Gaillot on 2018-11-13 15:50:02 UTC ---

Yes, that makes sense, done. We can let --quiet keep the current behavior.
Comment 2 Tomas Jelinek 2019-06-10 11:08:39 UTC 
This has been done in upstream some time ago: https://github.com/ClusterLabs/pcs/commit/601b765a662f4852d15be72074cff57df1864693 and it has been included in pcs packages since pcs-0.10.1-6.el8
Comment 7 errata-xmlrpc 2019-11-05 20:40:02 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:3311
Note You need to log in before you can comment on or make changes to this bug.