-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
puppet module install puppetlabs-firewall fails #228
Comments
Failes on Fedora 17 on my end as well: puppet module install puppetlabs/firewallNotice: Preparing to install into /etc/puppet/modules ... It does seem some files are missing: ls -l /etc/puppet/modules/firewall/total 48 The "manifests" directory seems to be missing. |
Having this problem as well. |
Weird, what version of puppet are you guys using? root@ubuntu-server-12042-x64-vbox4210:/# puppet module install puppetlabs-firewall I'm wondering if this is some weird bug specific to one version of puppet. |
I'm using Puppet 3.2.3 running on Ruby 1.9.3, Fedora 17. |
We're going to repackage and release a 0.4.1. I think it's related to checked out spec stuff breaking the package, as it makes a symlink to itself. Hopefully a repackage will magically fix it! |
Thanks, @apenney. I'm seeing the problem with librarian-puppet-maestrodev 0.9.9.8. Oddly enough, after a failed Puppetfile:
Output:
|
puppet --version3.0.0-rc8 ruby --versionruby 1.9.3p194 (2012-04-20 revision 35410) [i686-linux] facter | grep rubyversionrubyversion => 1.9.3 cat /etc/debian_version6.0.6 -- Hugh Esco On Fri, 09 Aug 2013 10:16:52 -0700
Hugh Esco |
Same issue here. |
Same issue on Ubuntu Precise 32-bit when deploying both with librarian-puppet (mod 'puppetlabs/firewall') and manually (sudo puppet module install puppetlabs/firewall --modulepath=/vagrant/modules --force) on a Vagrant VM. Error message: Error: No such file or directory - /vagrant/.tmp/librarian/cache/source/puppet/forge/3792e516e3ff92a0ef9f5e827f8e76eb/puppetlabs/firewall/version/9eac01120a372609e0afa3b236d9ed2d/firewall/spec/fixtures/modules/firewall/lib Error doesn't occur on the second run and module is installed successfully. Puppet version 2.7.19. |
Error still present for me with RHEL5.9 with a puppet 3.2.4 I checked the missing file, it is a link to an inexisting folder... |
Error still present here on RHEL5 with Puppet 3.2.2. [root@puppet modules]# puppet module --environment development install puppetlabs/firewall |
We think this is FINALLY fixed in 0.4.2. Somewhere along the way some changes to puppet module install made it break if it unpacked the symlink before the destination folder was on disk. I've removed those symlinks and now things seem happier. |
Totally fixed for me, works instantaneously and awesomely on RHEL5. |
@apenney I've run into this with several modules, and although the symlinks in the tarball are a problem, they're only a symptom. I'd say this is a bug in the puppet module tool, unfortunately. |
And I've found the existing issue: http://projects.puppetlabs.com/issues/17033 |
works here, on newly updated puppet version 3.3.0 git:/etc/puppet# puppet module install --force puppetlabs-firewall |
git:~# grep module_repository /etc/puppet/puppet.conf
module_repository = http://forge.puppetlabs.com
git:~# puppet module install puppetlabs/firewall
Preparing to install into /etc/puppet/modules/production ...
Error: No such file or directory - /etc/puppet/modules/production/firewall/CONTRIBUTING.md
Error: Try 'puppet help module install' for usage
git:~# puppet module install puppetlabs-firewall
Preparing to install into /etc/puppet/modules/production ...
Error: No such file or directory - /etc/puppet/modules/production/firewall/CONTRIBUTING.md
Error: Try 'puppet help module install' for usage
The text was updated successfully, but these errors were encountered: