Removal of num_updates in applying crm diff to cibadmin for configuration updates about crmsh HOT 3 CLOSED

Hi, the following commit should solve this issue: a73febc

It requires a version of Pacemaker which supports the --no-version argument.

Maybe stripping the num_updates from the XML before generating the diff is a viable option if not, I will look into this.

from crmsh.

Unfortunately the release version of Pacemaker 1.1.12 does not include --no-version.
I will take a look into the patch that includes this if it will be possible to use it with 1.1.12 and compile my own 1.1.12.
My systems are somehow Safety Relevant and therefore i cannot rely on recent development versions.
And gaoyan has applied a patch for assert failure in crm_element_value in case of no version information supplied.
The idea with checking epoch is not bad, it might not be a good idea to skip it completely, as done in the named patch.
It is just a bit to restrictive to check also the status update counter for updating the configuration.
The combination of Pacemaker >=1.1.10 and crmsh 1.2.x result in the described counter update.
cibadmin had incremented epoch and reset num_updates to 0.
It can be configurable by crm.conf, which type of version check shall be applied, full with both values, none as the patch above or "lazy" only epoch number.
Then, it is up to the user to decide which version security against duplicated updates he wants.

from crmsh.

This should be fixed by #75

from crmsh.