Support for Puppet 3.0

[antonlindstrom]

When running tests with rspec-puppet against Puppet 3.0 the run fails with the message:

Error converting value for param 'statedir': Could not find value for $vardir on node example.local

For example, I ran the test powerdns__package_spec.rb and got the following output:

1) powerdns::package 
   Failure/Error: it { should contain_package('pdns-server').with_ensure('present') }
   Puppet::Error:
     Error converting value for param 'statedir': Could not find value for $vardir on node example.local
   # ./spec/classes/powerdns__package_spec.rb:5:in `block (2 levels) in <top (required)>'

This may be related fixes: puppet issue 13429, mcollective-plugin PR 38.

Thanks!

[jumanjiman]

@antonlindstrom I found this issue via Google after encountering the same error you describe above.
The error went away after I updated the Gemfile in my puppet manifests repo as:

diff --git a/Gemfile b/Gemfile
index 74fa739..ba9a394 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,13 +1,18 @@
 source :rubygems
 gem "puppetlabs_spec_helper", "~>0.4"
-gem "mocha", "0.12.7"
-gem "rspec-core", "2.11.1"
+gem "mocha", "0.13.2"
+gem "rspec-core", "2.12.2"
+gem "rspec", "2.12.0"
+gem "rspec-expectations", "2.12.1"
+gem "rspec-mocks", "2.12.2"
 gem "puppet-lint", "~>0.3.2"
-gem "puppet", "~> 2.7.19"
-gem "rspec-puppet", "0.1.4"
-gem "hiera", "1.1.0"
+gem "puppet", "~> 3.0.2"
+gem "rspec-puppet", "~> 0.1"
+gem "hiera", "~> 1.0"
 gem "hiera-puppet", "1.0.0"
 gem "fastercsv", "1.5.5", :platforms => [:ruby_18, :mingw_18]
-gem "rspec-hiera-puppet", "0.3.0"
+gem "rspec-hiera-puppet", "~> 1.0.0"
 gem "open4", "1.3.0"
 gem "puppet-catalog-test", "0.1.0"
+gem "diff-lcs", ">= 1.1.3"
+gem "metaclass", "~> 0.0.1"

https://travis-ci.org/rodjek/rspec-puppet/jobs/4361531 shows that rspec-puppet succeeds on ruby 1.9.3 and puppet 3.0.0, so I ran bundler on my workstation within the rspec-puppet git repo. rake test worked locally, so I updated my Gemfile with the versions that I got when running bundler with rspec-puppet.

[antonlindstrom]

Cheers! Closing this issue.

[logicminds]

I know this issue is closed but have come across this issue with other code bases and found this issue to be helpful. The better fix is to do the following:

begin
    Puppet.initialize_settings
 rescue
        # do nothing otherwise calling init twice raises an error
 end