Created attachment 918398 [details]
proposed fix

Before Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.115-32.el7.x86_64
[root@rh70-node1 ~]# man pcs
{output trimmed}
       colocation set <resource1> <resource2> [resourceN]... [setoptions] ...
              [set <resourceX> <resourceY> ...] [setoptions <name>=<value>...]
              Create a colocation constraint with a resource set
{output trimmed}
[root@rh70-node1 ~]# pcs constraint colocation set dummy1 dummy2 setoptions sequential=true
Error: Unable to update cib
Call cib_replace failed (-203): Update does not conform to the configured schema
<cib admin_epoch="0" cib-last-written="Wed Sep 10 17:23:29 2014" crm_feature_set="3.0.7" epoch="6523" have-quorum="1" num_updates="1" update-client="cibadmin" update-origin="rh70-node1" validate-with="pacemaker-1.2" dc-uuid="1">
{output trimmed}

After Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.126-1.el7.x86_64
[root@rh70-node1 ~]# man pcs
{output trimmed}
       colocation  set  <resource1>  <resource2> [resourceN]... [options] [set
       <resourceX>    <resourceY>    ...    [options]]    [setoptions    [con‐
       straint_options]]
              Create  a  colocation  constraint with a resource set. Available
              options   are   sequential=true/false,   require-all=true/false,
              action=start/promote/demote/stop  and  role=Stopped/Started/Mas‐
              ter/Slave.  Available  constraint_options  are   score,   score-
              attribute and score-attribute-mangle.
{output trimmed}
[root@rh70-node1 ~]# pcs constraint colocation set dummy1 dummy2 setoptions sequential=true
Error: invalid option 'sequential', allowed options are: score, score-attribute, score-attribute-mangle
[root@rh70-node1 ~]# echo $?
1
[root@rh70-node1 ~]# pcs constraint colocation set dummy1 dummy2 sequential=true
[root@rh70-node1 ~]# echo $?
0
[root@rh70-node1 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
Colocation Constraints:
  Resource Sets:
    set dummy1 dummy2 sequential=true setoptions score=INFINITY

I have verified that setoptions parameter can be used according to the manual with pcs-0.9.137-11.el7.x86_64.

-----

[root@duck-01 ~]# rpm -q pcs
pcs-0.9.137-11.el7.x86_64

[root@duck-01 ~]# pcs constraint colocation -h

Usage: pcs constraint [constraints]...
    colocation show [--full]
        List all current colocation constraints (if '--full' is specified show
        the internal constraint id's as well).

    colocation add [master|slave] <source resource id> with [master|slave]
                   <target resource id> [score] [options] [id=constraint-id]
        Request <source resource> to run on the same node where pacemaker has
        determined <target resource> should run.  Positive values of score
        mean the resources should be run on the same node, negative values
        mean the resources should not be run on the same node.  Specifying
        'INFINITY' (or '-INFINITY') for the score force <source resource> to
        run (or not run) with <target resource>. (score defaults to "INFINITY")
        A role can be master or slave (if no role is specified, it defaults to
        'started').

    colocation set <resource1> <resource2> [resourceN]... [options]
               [set <resourceX> <resourceY> ... [options]]
               [setoptions [constraint_options]]
        Create a colocation constraint with a resource set.
        Available options are sequential=true/false, require-all=true/false,
        action=start/promote/demote/stop and role=Stopped/Started/Master/Slave.
        Available constraint_options are id, score, score-attribute and
        score-attribute-mangle.

    colocation remove <source resource id> <target resource id>
        Remove colocation constraints with <source resource>

[root@duck-01 ~]# pcs resource create dummy1 Dummy
[root@duck-01 ~]# pcs resource create dummy2 Dummy
[root@duck-01 ~]# pcs resource
 Clone Set: dlm-clone [dlm]
     Started: [ duck-01 duck-02 duck-03 ]
 Clone Set: clvmd-clone [clvmd]
     Started: [ duck-01 duck-02 duck-03 ]
 dummy1 (ocf::heartbeat:Dummy): Started 
 dummy2 (ocf::heartbeat:Dummy): Started 
[root@duck-01 ~]# pcs constraint colocation set dummy1 dummy2 setoptions sequential=true
Error: invalid option 'sequential', allowed options are: score, score-attribute, score-attribute-mangle, id
[root@duck-01 ~]# pcs constraint colocation set dummy1 dummy2 sequential=true
[root@duck-01 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start dlm-clone then start clvmd-clone (kind:Mandatory)
Colocation Constraints:
  clvmd-clone with dlm-clone (score:INFINITY)
  Resource Sets:
    set dummy1 dummy2 sequential=true setoptions score=INFINITY
[root@duck-01 ~]#

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/RHBA-2015-0415.html