Hi there,
Would anybody be willing to try to reproduce a bug please ?
You need 3 nodes to reproduce it.
It's using the dummy resource agent.
I'm using openais but i don't think that matters.
I'd like to know if you can reproduce the behavior when migrating
a resource.
here is the crm config to use:
property stonith-enabled="false"
property start-failure-is-fatal="false"
property default-resource-stickiness="5000"
property symmetric-cluster="true"
property no-quorum-policy="ignore"
primitive dom0-iscsi1-cnx1 ocf:heartbeat:Dummy
group dom0-iscsi1 dom0-iscsi1-cnx1
clone clone-dom0-iscsi1 dom0-iscsi1 \
meta clone-max="2" clone-node-max="1" globally-unique="false"
primitive domU-test01 ocf:heartbeat:Dummy \
meta allow-migrate="true"
order domU-test01-iscsi1-order1 0: clone-dom0-iscsi1 domU-test01
colocation domU-test01-iscsi1-colocation1 +inf: domU-test01
clone-dom0-iscsi1
And there are the steps:
- start domU-test01
- migrate it with "crm migrate domU-test01"
I'm expecting the resource to be migrated (without being stopped) to
where the other iscsi clone is running.
Could you tell me what's the behavior you're observing ?
Thanks in advance.
For more information, bug report is at:
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2167
--
Laurent
_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
