Issue #17543 has been reported by Ashley Penney. ---------------------------------------- Bug #17543: Puppet 3.0 rspec and custom resources no longer work https://projects.puppetlabs.com/issues/17543
Author: Ashley Penney Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Based on https://groups.google.com/forum/?fromgroups#!topic/puppet-users/l8jzYibbSL8 thread multiple users have reported they can no longer run their unit tests on modules. The problem lies in custom resources/functions, and can be easily tested with puppet 3.0 and puppetlabs-apt from github. When you run the tests you'll see failures along the lines of: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type anchor at /home/nrhuff/repos/puppet-os/spec/fixtures/modules/os/manifests/init.pp:2 on node enyo.localhost One of the users suffering this problem dug in further as mentioned on the list and said: <cite> So I dug into this a little more. It has something to do with how puppet is loading the type definitions. There appears to be some kind of cache that gets loaded with type definitions when the first manifest gets processed. If the first test that gets run is for a class that contains all the types necessary for classes that get tested later everything runs fine. If on the other hand if the first test run is for a class that doesn't contain all the types used in later classes the later test fails. </cite> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. 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-bugs?hl=en.
