Re: [Puppet Users] Re: puppetlabs-corosync: cs_property doesn't get set

2014-10-15 Thread ge...@riseup.net
Hi James, On 14-10-13 19:58:02, James Eckersall wrote: > I had issues when I was first using this module with the primitives. After fixing the issue with cs_property, I'm now running into the same problem like you. Despite cs_primitive being defined in puppet, it doesn't get created. Did you chan

Re: [Puppet Users] puppetlabs-corosync: cs_property doesn't get set

2014-10-15 Thread ge...@riseup.net
Hi, On 14-10-08 22:57:33, ge...@riseup.net wrote: > I'm running Debian wheezy, puppet version 2.7.23. I wanted to have a > look at the corosync module provided by puppetlabs [1]. > > [...] > > After the agent run, corosync and pacemaker gets installed, and the > cl

Re: [Puppet Users] Re: puppetlabs-corosync: cs_property doesn't get set

2014-10-13 Thread ge...@riseup.net
Hi, On 14-10-13 05:58:06, james.eckers...@fasthosts.com wrote: > Since you aren't getting any errors, it would suggest to me that puppet > thinks those values are already set correctly and therefore require no > further action. > The module essentially parses the output from "crm configure show

Re: [Puppet Users] Re: puppetlabs-corosync: cs_property doesn't get set

2014-10-13 Thread ge...@riseup.net
Hi James, On 14-10-13 01:27:05, james.eckers...@fasthosts.com wrote: > Try running the agent with --debug and --evaltrace to identify what Puppet > is doing in relation to those resources. Thanks for your help. The log shows multiple lines like: Mon Oct 13 13:40:11 +0200 2014 Cs_property[stonith

[Puppet Users] puppetlabs-corosync: cs_property doesn't get set

2014-10-08 Thread ge...@riseup.net
[I'm quite new to puppet, so not sure if this is an appropriate question for this list.] Hi all, I'm running Debian wheezy, puppet version 2.7.23. I wanted to have a look at the corosync module provided by puppetlabs [1]. My code for the test looks quite simple: class { 'corosync': enable_secau