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 1182986 - Unable to find out value for require-all parameter for ordering constraint with clones
Summary: Unable to find out value for require-all parameter for ordering constraint wi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-16 11:35 UTC by michal novacek
Modified: 2015-11-19 09:34 UTC (History)
4 users (show)

Fixed In Version: pcs-0.9.140-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: User creates an ordering constraint and specifies the require-all parameter for it. Consequence: The require-all parameter is missing in constraints listing. Fix: Display the require-all parameter in ordering constraints listing. Result: User knows the value of require-all parameter of ordering constraints.
Clone Of:
Environment:
Last Closed: 2015-11-19 09:34:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (5.33 KB, patch)
2015-05-28 11:53 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2290 0 normal SHIPPED_LIVE Moderate: pcs security, bug fix, and enhancement update 2015-11-19 09:43:53 UTC

Description michal novacek 2015-01-16 11:35:08 UTC 
Description of problem:
It is possible to specify require-all=true option when creating ordering constraint but it cannot be later find out in any of the output of pcs. I would want to see it in 'pcs constraint list --full'.

Version-Release number of selected component (if applicable):
pcs-0.9.137-10.el7.x86_64

How reproducible: always

Steps to Reproduce:
1. pcs constraint order a-clone then b-clone require-all=false

Actual results: Not able to find out the value of require-all for ordering constraint

Expected results: See require-all value in 'pcs constraint list --full'
Comment 2 Tomas Jelinek 2015-05-28 11:53:48 UTC 
Created attachment 1031227 [details]
proposed fix
Comment 3 Tomas Jelinek 2015-06-04 14:38:12 UTC 
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.137-13.el7_1.2.x86_64
[root@rh71-node1:~]# pcs resource create d1 dummy --clone
[root@rh71-node1:~]# pcs resource create d2 dummy --clone
[root@rh71-node1:~]# pcs constraint order d1-clone then d2-clone require-all=false
Adding d1-clone d2-clone (kind: Mandatory) (Options: require-all=false first-action=start then-action=start)
[root@rh71-node1:~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start d1-clone then start d2-clone (kind:Mandatory)
Colocation Constraints:



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.140-1.el6.x86_64
[root@rh71-node1:~]# pcs resource create d1 dummy --clone
[root@rh71-node1:~]# pcs resource create d2 dummy --clone
[root@rh71-node1:~]# pcs constraint order d1-clone then d2-clone require-all=false
Adding d1-clone d2-clone (kind: Mandatory) (Options: require-all=false first-action=start then-action=start)
[root@rh71-node1:~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start d1-clone then start d2-clone (kind:Mandatory) (Options: require-all=false)
Colocation Constraints:
Comment 5 Miroslav Lisik 2015-07-16 14:30:39 UTC 
Marking VERIFIED in pcs-0.9.142-2.el7.x86_64

BEFORE FIX:
[root@virt-080 ~]# rpm -q pcs
pcs-0.9.137-13.el7.x86_64
[root@virt-080 ~]# pcs resource create dummy-1 Dummy --clone
[root@virt-080 ~]# pcs resource create dummy-2 Dummy --clone
[root@virt-080 ~]# pcs resource show
 Clone Set: dummy-1-clone [dummy-1]
     Started: [ virt-080 virt-081 virt-082 ]
 Clone Set: dummy-2-clone [dummy-2]
     Started: [ virt-080 virt-081 virt-082 ]
[root@virt-080 ~]# pcs constraint 
Location Constraints:
Ordering Constraints:
Colocation Constraints:
[root@virt-080 ~]# pcs constraint order dummy-1-clone then dummy-2-clone require-all=true
Adding dummy-1-clone dummy-2-clone (kind: Mandatory) (Options: require-all=true first-action=start then-action=start)
[root@virt-080 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start dummy-1-clone then start dummy-2-clone (kind:Mandatory)
Colocation Constraints:

No constraint options listed.

AFTER FIX:
[root@virt-080 ~]# rpm -q pcs
pcs-0.9.142-2.el7.x86_64
[root@virt-080 ~]# pcs resource create dummy-1 Dummy --clone
[root@virt-080 ~]# pcs resource create dummy-2 Dummy --clone
[root@virt-080 ~]# pcs resource show
 Clone Set: dummy-1-clone [dummy-1]
     Started: [ virt-080 virt-081 virt-082 ]
 Clone Set: dummy-2-clone [dummy-2]
     Started: [ virt-080 virt-081 virt-082 ]
[root@virt-080 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
Colocation Constraints:
[root@virt-080 ~]# pcs constraint order dummy-1-clone then dummy-2-clone require-all=true
Adding dummy-1-clone dummy-2-clone (kind: Mandatory) (Options: require-all=true first-action=start then-action=start)
[root@virt-080 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start dummy-1-clone then start dummy-2-clone (kind:Mandatory) (Options: require-all=true)
Colocation Constraints:

Constraint option 'require-all' is listed in Options section.
Comment 7 errata-xmlrpc 2015-11-19 09:34:14 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://rhn.redhat.com/errata/RHSA-2015-2290.html
Note You need to log in before you can comment on or make changes to this bug.