Hi, On Wed, May 15, 2013 at 02:02:46PM +0200, Ulrich Windl wrote: > >>> Lars Marowsky-Bree <l...@suse.com> schrieb am 15.05.2013 um 10:35 in > >>> Nachricht > <20130515083509.gp3...@suse.de>: > > On 2013-05-15T09:53:31, Ulrich Windl <ulrich.wi...@rz.uni-regensburg.de> > > wrote: > > > >> Hi! > >> > >> I think there is a bug in crm shell's "rename": > >> I renamed a colocation constraint named "col_Xen_VMs_cfs2" to > > "col_Xen_VMs_cfs_mir" > >> > >> After that I see: > >> <rsc_colocation id="col_Xen_VMs_cfs_mir" (...) > >> <resource_set id="col_Xen_VMs_cfs2-0" sequential="false" > > >> (...) > >> > >> I wonder: Shouldn't the resource_set id be renamed as well? > > > > No. There's not really a reason to do that, the set id isn't exposed by > > the shell, or is it?
Right. > > Rename isn't recursive. > > So if I rename A to B, then create a new A, there won't be any conflict? I hope so ;-) > AFAIR, id must be unique. Yes, that's true. Thanks, Dejan > Regards, > Ulrich > > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
