Red Hat Bugzilla – Bug 1182986
Unable to find out value for require-all parameter for ordering constraint with clones
Last modified: 2015-11-19 04:34:14 EST
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'
Created attachment 1031227 [details] proposed fix
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:
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.
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