28.06.2013 17:47, Dejan Muhamedagic wrote: ... > If you want to test here's a new patch. It does work with > unrelated changes happening in the meantime. I didn't test yet > really concurrent updates. >
One thing I see immediately, is that node utilization attributes are deleted after I do 'load update' with empty node utilization sections. That is probably not specific to this patch. I have that attributes dynamic, set from a RA (as node configuration may vary, I prefer to detect how much CPU and RAM I have and set utilization accordingly rather then put every hardware change into CIB). On the one hand, I would agree that crmsh does what is intended - if no utilization attributes is set in a config update, then they shoud be removed. On the other, I would prefer to delete node utilization attributes on update only if new definition contains 'utilization' section but without that attributes. Or may be it is possible to use transient utilization attributes? I don't think so... Ugh, that would be nice. Everything else works fine, I was able to do: # crm configure crm(live)configure# edit <edit target-role attribute on a clone> In other shell: crm resource stop... crm(live)configure# commit And that didn't produce any errors. Both actions completed correctly. Vladislav _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
