Incomplete support for Corosync 2.x

[voxpupuli]

Incomplete support for Corosync 2.x

[sammcj]

We had this exact issue with the puppet module yesterday! Thank you for the info @fghaas - hopefully this can be patched soon?

[fghaas]

@sammcj I'm not entirely sure how much work it would be; particularly getting the autodependencies right is probably somewhat invasive. Does the suggested workaround work for you, i.e. adding service { 'pacemaker': } and then require => Service['pacemaker'] on the cs_ resource types?

[sammcj]

@fghaas not really - it seems the module is missing a lot of logic around dealing with pcs in general. We've just installed crmsh from SUSE on CentOS 7 and forced the module to use crm instead which works 'alright'.

[fghaas]

@sammcj Elaborate please? I'm running this module (from git master; 0.7.0 is broken as per #144) with pcs and haven't run into major snags yet.

[ffrank]

For the time being, the most economic workaround for users who don't rely on virtual resources will be

Service['pacemaker'] -> Cs_location<| |>

etc. for each cs_* type.

[fghaas]

Well yes that's true, but I'm still curious as to what other missing logic @sammcj is referring to.

[ffrank]

Depending on the scope of that, I'd like to have a new 'pcs provider is not up to par with crm' issue for that, so as not to fuzz the conversation here too much.

[fghaas]

If it indeed is not.

[jyaworski]

Is this still an issue?

[roidelapluie]

Will be closed by #245.