Hi Jan,
I think I found the reason for this. Looking at rdoinfo (the source of information for what we build in RDO) I found this: [1]. The tags in the YAML file mean that we are building puppet-pacemaker 0.4.0 in RDO Newton, and 0.5.0 in Ocata. It looks like the patch you need in puppet-pacemaker is already available in 0.5.0, see [2].
To make things more interesting, the RDO Trunk builds use the same stable branch for both Newton and Ocata, and it's stable/0.6.x. This branch is more recent than what we ship in RDO.
So, TL;DR: we can propose two different fixes here:
b) For a stable fix, we should at least bump the puppet-pacemaker version we are shipping in Newton to 0.5.0, to match the Ocata version and fix the deployment issue.
Haikel, what do you think?
Regards,
Javier
[1] - https://github.com/redhat-openstack/rdoinfo/blob/master/rdo.yml#L1275-L1293
[2] - https://review.openstack.org/422484
_______________________________________________
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users
To unsubscribe: users-unsubscribe@lists.rdoproject.org