[Pacemaker] Centos 70->71 update fails with "Application of an update diff failed (rc=-206)"

[Andrew Beekhof]

> On 27 Apr 2015, at 6:35 pm, Patrick Zwahlen <paz at navixia.com> wrote:
> 
>> Apart from those scary logs, does anything actually break?
>> What your seeing is probably just ignorable noise from the older version
>> - I would expect the underlying cib to resolve things correctly.
> 
> Thanks Andrew for the response.
> 
> After starting the new 1.1.12 and trying to migrate my resources, I ended up
> with groups stuck "halfway" with some resources stopped on the old node and
> no migration (apparently without errors from my RA).

If you’d like to send a crm_report I’d be interested to have a look.

> 
> This WE I tried another route, as I finally found how to upgrade *just*
> corosync/pacemaker (without the whole OS).
> 
> - enter maintenance
> - "pcs cluser stop --all"
> - "yum update corosync pacemaker libqb resource-agents pcs"
> - "pcs cluser start --all"
> - exit maintenance
> 
> I initially just did a "yum update corosync pacemaker" and then pacemaker
> didn't start. I was missing libqb but I also think there a dependency
> missing somewhere in the RPMs, as libqb should get updated as well.

Nod.  We’re adding that in.
Both sides keep maintaining backwards compatibility - pacemaker just wants to use the version it was built against but rpm isn’t smart enough to do that automagically :-(

> 
> Anyway, I have been able to migrate from CentOS 7.0 to 7.1 in my lab without
> losing anything.

Excellent.  Sounds like it might have been something to do with the resources themselves then :-/

> 
> Cheers, Patrick
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org