On Tuesday, August 21, 2012 12:16:50 AM UTC-5, llowder wrote: > > > > On Monday, August 20, 2012 6:59:55 PM UTC-5, Andy Parker wrote: >> >> Parsing that whole mess apart it looks like you have 3 failures (in >> the stack trace they should up as the "F" right after >> "/usr/bin/rspec:19") where the stacktrace of what went wrong in each >> case is between the "/usr/bin/rspec:19" and the >> "/var/lib/gems/1.8/gems/hiera-0.3.0/lib/hiera/backend.rb:12:in >> `datadir'" above it. > > > Yeah, my rspec test has 3 sections, so the class would be called 3 times, > so it makes sense that the same error would be repeated three times, in > three different lines. > > > >> The most interesting thing for each stack trace >> is that they all go through your spec file >> (/etc/puppet/environments/test/modules/elasticsearch/spec/classes/elasticsearch_spec.rb) >> >> >> at the same lines that rspec is reporting for the failures (58, 36, >> and 15). Top of the stacktrace shows where the error occurred: >> /var/lib/gems/1.8/gems/hiera-0.3.0/lib/hiera/backend.rb:12:in >> `datadir', which is the same each time. Taking a look at that code in >> hiera 0.3.0 ( >> https://github.com/puppetlabs/hiera/blob/v0.3.0/lib/hiera/backend.rb#L12) >> >> shows 2 calls of '[]' to access the Config. We can tell that Config is >> not the nil in this case because to reach that line it had to execute >> `Config.include?` on the previous line. That means that >> `Config[backend]` is what has returned nil. >> >> > That's interesting. > >> As you said, you started getting the error when you started using >> hiera. I think this points to not having hiera properly configured. >> Now if only this had been a little easier to track down :) >> >> > In my .fixtures.yaml I am using a symlink rather than a git repo for my > stdlib and hiera-puppet usage. I think, however, what I need to do is > adjust the hiera.yaml used in the tests, but at least now I know where to > look and what direction to head. > > Thank you very much. > > Just for future reference, the problem was that when I copied in the hiera.yaml from the patch, the spacing got messed up and so my hiera.yaml was invalid, and it wasn't finding the hierarchy or the datadir I had defined. Fixing that corrected the problems.
thanks for all the help. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/2dYIXiQsaaAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
