Yes that was done in a module created by PDK originally. Here is the debug output
peter@saltycowdawg: mediawiki]:(master): pdk test unit --debug pdk (INFO): Using Ruby 2.5.1 pdk (INFO): Using Puppet 6.0.2 pdk (DEBUG): Checking for missing Gemfile dependencies. pdk (DEBUG): Using '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle' from PDK package. pdk (DEBUG): Executing '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle check --gemfile=/home/peter/prj-src/puppet/mediawiki/Gemfile --dry-run' pdk (DEBUG): Command environment: pdk (DEBUG): PUPPET_GEM_VERSION: 6.0.2 pdk (DEBUG): BUNDLE_IGNORE_CONFIG: 1 pdk (DEBUG): GEM_HOME: /home/peter/.pdk/cache/ruby/2.5.0 pdk (DEBUG): GEM_PATH: /opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0 pdk (DEBUG): PATH: /opt/puppetlabs/pdk/private/ruby/2.5.1/bin:/home/peter/.pdk/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0/bin:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0/bin:/opt/puppetlabs/pdk/bin:/home/peter/bin:/home/peter/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/puppetlabs/bin:/opt/puppetlabs/pdk/private/git/bin pdk (DEBUG): Execution of '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle check --gemfile=/home/peter/prj-src/puppet/mediawiki/Gemfile --dry-run' complete (duration: 2.847360904s; exit code: 0) pdk (DEBUG): Updating Gemfile dependencies. pdk (DEBUG): Using '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle' from PDK package. pdk (DEBUG): Executing '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle lock --lockfile=/home/peter/prj-src/puppet/mediawiki/Gemfile.lock --update --local' pdk (DEBUG): Command environment: pdk (DEBUG): BUNDLE_GEMFILE: /home/peter/prj-src/puppet/mediawiki/Gemfile pdk (DEBUG): PUPPET_GEM_VERSION: 6.0.2 pdk (DEBUG): BUNDLE_IGNORE_CONFIG: 1 pdk (DEBUG): GEM_HOME: /home/peter/.pdk/cache/ruby/2.5.0 pdk (DEBUG): GEM_PATH: /opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0 pdk (DEBUG): PATH: /opt/puppetlabs/pdk/private/ruby/2.5.1/bin:/home/peter/.pdk/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0/bin:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0/bin:/opt/puppetlabs/pdk/bin:/home/peter/bin:/home/peter/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/puppetlabs/bin:/opt/puppetlabs/pdk/private/git/bin pdk (DEBUG): Execution of '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle lock --lockfile=/home/peter/prj-src/puppet/mediawiki/Gemfile.lock --update --local' complete (duration: 0.22216318s; exit code: 1) pdk (FATAL): /opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:289:in `find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException) from /opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:308:in `activate_bin_path' from /opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle:23:in `<main>' pdk (FATAL): Unable to resolve Gemfile dependencies. pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/util/bundler.rb:185:in `update_lock!' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/util/bundler.rb:46:in `ensure_bundle!' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/cli/test/unit.rb:76:in `block (2 levels) in <module:CLI>' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:329:in `run_this' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:269:in `run' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:287:in `run' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:287:in `run' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/cli.rb:18:in `run' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/exe/pdk:6:in `<top (required)>' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/bin/pdk:23:in `load' pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/bin/pdk:23:in `<main>' On Mon, Jan 28, 2019 at 4:27 AM David Schmitt <david.schm...@puppet.com> wrote: > Hi Peter, > > is the module compatible to the PDK? That is, have you created the module > with the PDK, and/or ran `pdk convert`/`pdk update` successfully on it? > > If no, please do so before trying to run any other PDK commands in a > module. > > If yes, please capture the full output of the command you're running after > adding `--debug`, and - for this specific case - the Gemfile. With that > information we'll have a better chance of figuring out what's going on > there. > > > Cheers, David > > On Sat, Jan 26, 2019 at 3:43 PM Peter Berghold <salty.cowd...@gmail.com> > wrote: > >> When I run "pdk test unit" I get the following error: >> pdk (INFO): Using Ruby 2.5.1 >> pdk (INFO): Using Puppet 6.0.2 >> pdk (FATAL): >> /opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:289:in >> `find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundle >> (Gem::GemNotFoundException) >> from >> /opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:308:in >> `activate_bin_path' >> from /opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle:23:in `<main>' >> >> pdk (FATAL): Unable to resolve Gemfile dependencies. >> >> I did a "gem list" and bundler is installed. What is the magic foo that I >> can do to make this work? >> >> >> -- >> >> Peter L. Berghold salty.cowd...@gmail.com >> >> h <http://blog.berghold.net>ttp://science-fiction.berghold.net >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/CAArvnv1gacMoibL%3DZm9D_icP%2Bse5WvWsiSFMnp69GF2yzSra%3DQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/puppet-users/CAArvnv1gacMoibL%3DZm9D_icP%2Bse5WvWsiSFMnp69GF2yzSra%3DQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > Cheers, David > > https://twitter.com/dev_el_ops > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CALF7fHafxdimbH6KfORRtK3LMRm5zRr8s9cOi_WCd3avYJg93g%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CALF7fHafxdimbH6KfORRtK3LMRm5zRr8s9cOi_WCd3avYJg93g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Peter L. Berghold salty.cowd...@gmail.com h <http://blog.berghold.net>ttp://science-fiction.berghold.net -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAArvnv2u374gUyMEdXonyU_ubbStyyhGziFDqaa9%3D5JOxovt6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
