Bug 1182986

Summary: Unable to find out value for require-all parameter for ordering constraint with clones
Product: Red Hat Enterprise Linux 7 Reporter: michal novacek <mnovacek>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.1CC: cluster-maint, mlisik, rsteiger, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 09:34:14 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:
Attachments:
Description Flags
proposed fix none

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