On Tue, 24 Dec 2013 14:41:20 +0300
Vladislav Bogdanov bub...@hoster-ok.com wrote:
I would expect that only one option is modified, but crmsh intend to
remove all others.
May be it is possible to fix it by one-line crmsh patch?
Kristoffer, Dejan?
Best,
Vladislav
Hi,
This was
02.01.2014 12:53, Kristoffer Grönlund wrote:
On Tue, 24 Dec 2013 14:41:20 +0300
Vladislav Bogdanov bub...@hoster-ok.com wrote:
I would expect that only one option is modified, but crmsh intend to
remove all others.
May be it is possible to fix it by one-line crmsh patch?
Kristoffer,
On Tue, 24 Dec 2013 14:41:20 +0300
Vladislav Bogdanov bub...@hoster-ok.com wrote:
I would expect that only one option is modified, but crmsh intend to
remove all others.
May be it is possible to fix it by one-line crmsh patch?
Kristoffer, Dejan?
Hi,
Yes, the intended behavior is for
20.12.2013 14:15, Vladislav Bogdanov wrote:
Hi all,
Just discovered that it is possible to remove options in subject with
admin action (at least with cibadmin --patch).
This is notably annoying when updating CIB with 'crm configure load
update' (which uses crm_diff to create patch) when
Hi all,
Just discovered that it is possible to remove options in subject with
admin action (at least with cibadmin --patch).
This is notably annoying when updating CIB with 'crm configure load
update' (which uses crm_diff to create patch) when updating other
cluster options.
While most (all?)
