[PUP-4427] Rake Spec tests fail due to missing dependencies Created: 2015/04/16  Updated: 2019/04/04  Resolved: 2016/04/20

Status: Closed
Project: Puppet
Component/s: Types and Providers
Affects Version/s: PUP 4.0.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Bryan Stopp Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Vagrant/VirtualBox CentOS-64 virtual machine;

Story Points: 3
QA Contact: Eric Thompson


When running rake/rspec tests, they fail due to an inability to find the plist gem. This only happens on 4.0.0. A good test case is the puppetlabs-tomcat module. I was able to take a baseline puppet VM (same one specified in my environment); get all of the gems installed; when i ran:

rake spec

I got this error:

Could not autoload puppet/type/user: Could not autoload puppet/provider/user/directoryservice: cannot load such file – plist on node localhost.localdomain.

If you change the version of puppet to be max of 3.7.4; it succeeds (plist is coming from facter/utils).

If you leave the version of puppet to 4.0.0 and install plist manually, the test passes, but with some warnings (other errors appear but i'm not seeing them on my module):

/usr/share/ruby/vendor_ruby/facter/util/plist/parser.rb:67: warning: already initialized constant Plist::StreamParser::TEXT
/usr/local/share/gems/gems/plist-3.1.0/lib/plist/parser.rb:75: warning: previous definition of TEXT was here
/usr/share/ruby/vendor_ruby/facter/util/plist/parser.rb:68: warning: already initialized constant Plist::StreamParser::XMLDECL_PATTERN
/usr/local/share/gems/gems/plist-3.1.0/lib/plist/parser.rb:76: warning: previous definition of XMLDECL_PATTERN was here
/usr/share/ruby/vendor_ruby/facter/util/plist/parser.rb:69: warning: already initialized constant Plist::StreamParser::DOCTYPE_PATTERN
/usr/local/share/gems/gems/plist-3.1.0/lib/plist/parser.rb:77: warning: previous definition of DOCTYPE_PATTERN was here
/usr/share/ruby/vendor_ruby/facter/util/plist/parser.rb:70: warning: already initialized constant Plist::StreamParser::COMMENT_START
/usr/local/share/gems/gems/plist-3.1.0/lib/plist/parser.rb:78: warning: previous definition of COMMENT_START was here
/usr/share/ruby/vendor_ruby/facter/util/plist/parser.rb:71: warning: already initialized constant Plist::StreamParser::COMMENT_END
/usr/local/share/gems/gems/plist-3.1.0/lib/plist/parser.rb:79: warning: previous definition of COMMENT_END was here
/usr/share/ruby/vendor_ruby/facter/util/plist.rb:21: warning: already initialized constant Plist::VERSION
/usr/local/share/gems/gems/plist-3.1.0/lib/plist.rb:20: warning: previous definition of VERSION was here

i don't know what all is affected by this, i just know this currently causes my tests to fail when testing against 4.0;

Commit which changed the configs: https://github.com/puppetlabs/puppet/commit/d5b3c48fe0a297aa392020622b6089a7508851a5

Comment by Kylo Ginsberg [ 2015/04/16 ]

I don't quite understand why this is happening either. But I'd like to.

Comment by Branan Riley [ 2016/04/20 ]

Bryan Stopp Hey, I'm going through our open tickets trying to find out what's still valid. Have you encountered this again and/or is it still a problem. If so can you provide any more info (a failure from a more modern version of puppet would be great).


Comment by Bryan Stopp [ 2016/04/20 ]

You know, i haven't run into the problem in a while, and i've moved computers/OS/VMs/versions/etc since this was created. So you can probably call it fixed through normal course of updating to new releases of Puppet.

Comment by Branan Riley [ 2016/04/20 ]

That's what I like to hear. Thanks for the prompt response

Generated at Mon Sep 28 06:34:43 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.