search

rodjek / librarian-puppet

http://librarian-puppet.com
MIT License
693 stars 209 forks source link

Parameter --use-v1-api doesn't work with Puppet >=3.6 #263

Closed jlyheden closed 9 years ago

jlyheden commented 9 years ago

Output from librarian-puppet install run using custom private forge and resolving dependencies from metadata.json:

-bash-4.1$ /usr/local/bin/bundle exec librarian-puppet install --use-v1-api --path spec/fixtures/modules
Error executing puppet module install. Check that this command succeeds:
puppet module install --version 4.3.2 --target-dir /var/lib/jenkins/jobs/puppet-module-profile/workspace/.tmp/librarian/cache/source/puppet/forge/10_1_2_102/puppetlabs-stdlib/4.3.2 --module_repository http://10.1.2.102 --modulepath /var/lib/jenkins/jobs/puppet-module-profile/workspace/.tmp/librarian/cache/source/puppet/forge/10_1_2_102/puppetlabs-stdlib/4.3.2 --module_working_dir /var/lib/jenkins/jobs/puppet-module-profile/workspace/.tmp/librarian/cache/source/puppet/forge/10_1_2_102/puppetlabs-stdlib/4.3.2 --ignore-dependencies puppetlabs-stdlib
Error:
Error: Request to Puppet Forge failed.
  The server being queried was http://10.1.2.102/v3/releases?module=puppetlabs-stdlib
  The HTTP response we received was '404 Not Found'

Downgrading to Puppet 3.5.1 sorts the issue. I guess the problem stems from that librarian-puppet wraps the "puppet module install" command when installing forge modules.

carlossg commented 9 years ago

puppet module tool 3.6+ will always use the v3 API