[Pacemaker] Collocation Resources

[Andrew Beekhof]

On Wed, Mar 24, 2010 at 12:43 AM, Travis Dolan <travis at mylasso.com> wrote:
> I would like to know if it is possible to configure more than two resources
> within a collocation group.
>
> Simply put I have 10 Virtual IPs that will need to migrate from Node A to
> Node B in the event of any failures. I also need these IPs to all start on
> the same Node in the event that both Nodes are knocked out, then come back
> online (ie. my cage goes dark).
>
> My existing config is below...
>
> node wsa \
>         attributes standby="off"
> node wsb \
>         attributes standby="off"
> primitive ip1 ocf:heartbeat:IPaddr2 \
>         params ip="10.0.1.10" cidr_netmask="24" nic="eth0:1" \
>         op monitor interval="30"
> primitive ip2 ocf:heartbeat:IPaddr2 \
>         params ip="10.0.1.11" cidr_netmask="24" nic="eth0:2" \
>         op monitor interval="30"
> primitive ip3 ocf:heartbeat:IPaddr2 \
>         params ip="10.0.1.12" cidr_netmask="24" nic="eth0:3" \
>         op monitor interval="30"
> primitive ip4 ocf:heartbeat:IPaddr2 \
>         params ip="10.0.1.13" cidr_netmask="24" nic="eth0:4" \
>         op monitor interval="30"
> colocation all-ips inf: ip1 ip2 ip3 ip4
> property $id="cib-bootstrap-options" \
>         dc-version="1.0.8-2a76c6ac04bcccf42b89a08e55bfbd90da2fb49a" \
>         cluster-infrastructure="openais" \
>         expected-quorum-votes="2" \
>         stonith-enabled="false" \
>         no-quorum-policy="ignore"
> rsc_defaults $id="rsc-options" \
>         resource-stickiness="100"
>
> If I stop corosync from running on either node, the IPs are migrated without
> issue. The problem occures when both nodes come up at or close to the same
> time. An example of this would be...
>
> Node A
> /etc/init.d/corosync stop
>
> Node B
> /etc/init.d/corosync stop
>
> Node A
> /etc/init.d/corosync start
>
> Node B
> /etc/init.d/corosync start
>
> Result
> ---------
>
> Online: [ wsa wsb ]
>
> ip1     (ocf::heartbeat:IPaddr2):       Started wsa
> ip2     (ocf::heartbeat:IPaddr2):       Started wsb
> ip3     (ocf::heartbeat:IPaddr2):       Started wsa
> ip4     (ocf::heartbeat:IPaddr2):       Started wsb
>

Looks like a bug somewhere.
Could you create a hb_report archive covering the test scenario
described above and attach it to a new bugzilla please?