Eric Robinson <eric.robin...@psmnv.com> writes: >> crm configure show xml c_clust19 > > Here is what I am entering using crmsh (version 2.0-1): > > > colocation c_clust19 inf: [ p_mysql_057 p_mysql_092 p_mysql_187 ] > p_vip_clust19 p_fs_clust19 p_lv_on_drbd0 ms_drbd0:Master > order o_clust19 inf: ms_drbd0:promote p_lv_on_drbd0 p_fs_clust19 > p_vip_clust19 [ p_mysql_057 p_mysql_092 p_mysql_187 ] > > > After I save it, I get no errors, but it converts it to this... > > > colocation c_clust19 inf: [ p_mysql_057 p_mysql_092 p_mysql_187 ] ( > p_vip_clust19:Master p_fs_clust19:Master p_lv_on_drbd0:Master ) ( > ms_drbd0:Master ) > order o_clust19 inf: ms_drbd0:promote ( p_lv_on_drbd0:start > p_fs_clust19:start p_vip_clust19:start ) [ p_mysql_057 p_mysql_092 > p_mysql_187 ] > > This looks incorrect to me. > > Here is the xml that it generates. > > <constraints> > <rsc_colocation id="c_clust19" score="INFINITY"> > <resource_set require-all="false" sequential="false" id="c_clust19-0"> > <resource_ref id="p_mysql_057"/> > <resource_ref id="p_mysql_092"/> > <resource_ref id="p_mysql_187"/> > <resource_ref id="p_mysql_213"/> > <resource_ref id="p_mysql_250"/> > <resource_ref id="p_mysql_289"/> > <resource_ref id="p_mysql_312"/> > <resource_ref id="p_mysql_702"/> > <resource_ref id="p_mysql_743"/> > <resource_ref id="p_mysql_745"/> > <resource_ref id="p_mysql_746"/> > <resource_ref id="p_mysql_747"/> > <resource_ref id="p_mysql_748"/> > </resource_set> > <resource_set id="c_clust19-1" sequential="false" role="Master"> > <resource_ref id="p_vip_clust19"/> > <resource_ref id="p_fs_clust19"/> > <resource_ref id="p_lv_on_drbd0"/> > </resource_set> > <resource_set role="Master" id="c_clust19-2" sequential="false"> > <resource_ref id="ms_drbd0"/> > </resource_set> > </rsc_colocation> > </constraints> > > The resources in set c_clust19-1 should start sequentially, starting with > p_lv_on_drbd0 and ending with p_vip_clust19. I also don't understand why > p_lv_on_drbd0 and p_vip_clust19 are getting the Master designation.
Hi, Yeah, that does indeed look like a bug.. One thing that is confusing and may be one reason why things get split in an unexpected way is because as you can see, the role attribute is applied per resource set, while it looks like it applies per resource in the crmsh syntax. So the shell does some complex logic to "split" sets based on role assignment. Cheers, Kristoffer > > -- > Eric Robinson > > -- // Kristoffer Grönlund // kgronl...@suse.com _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
