Bug(?) in puppetlabs-firewall module prevents successful install/upgrade to PE 3.2

[Peter Bukowinski]

When upgrading my master from 3.1 to 3.2 (on a Scientific Linux 6.3 server), the install fails during the puppetlabs-firewall module installation with this error:

** /opt/puppet/bin/puppet module install "/misc/local/pe/puppet-enterprise-3.2.0-el-6-x86_64/modules/puppetlabs-firewall-1.0.0.tar.gz" --force --ignore-dependencies --modulepath /opt/puppet/share/puppet/modules

Notice: Preparing to install into /opt/puppet/share/puppet/modules ...

Notice: Installing -- do not interrupt ...

Error: No such file or directory - /opt/puppet/share/puppet/modules/firewall/spec/acceptance/nodesets/default.yml

When I look in the nodesets directory, I see a broken symlink that looks like it may be missing a "-pe" in its name:

>ls -la /opt/puppet/share/puppet/modules/firewall/spec/acceptance/nodesets/

total 20

drwxr-xr-x 2 root root 4096 Mar  4 12:40 .

drwxr-xr-x 3 root root 4096 Mar  4 12:40 ..

-r--r--r-- 1 root root  282 Jan 30 12:12 centos-64-x64-pe.yml

lrwxrwxrwx 1 root root   17 Mar  4 12:40 default.yml -> centos-64-x64.yml

-r--r--r-- 1 root root  254 Jan 30 12:12 sles-11sp1-x64.yml

-r--r--r-- 1 root root  285 Jan 30 12:12 ubuntu-server-10044-x64.yml

Has anyone else run into this? In any case, I'd recommend waiting to upgrade until you hear otherwise. 

--

Peter Bukowinski

[Matthaus Owens]

Peter,
I've opened https://tickets.puppetlabs.com/browse/ENTERPRISE-88 to
track this issue. It seems related to
https://tickets.puppetlabs.com/browse/MODULES-473.

> --
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/F9979BCD-D5CE-4906-91DD-6DE388D6665E%40gmail.com.
> For more options, visit https://groups.google.com/groups/opt_out.



--
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save $350!

[Paul Greenbank]

Hey Peter

As a work around I've downloaded the latest 1.0.2 firewall module from puppetforge backed up the broken module in the installer module directory copied the 1.0.2 version into the modules directory renamed it (yes this is probably a very bad thing !) to 1.0.0 which the installer expects and re-run the install and presto the install completes.

You maybe able to hack the installer script to use the 1.0.2 file name but I'm working on a test box so a quick and dirty hack with the file name did the job for me.

Cheers

[Peter Bukowinski]

On Mar 6, 2014, at 4:58 PM, Paul Greenbank <paul.gr...@gmail.com> wrote:

> Hey Peter
>
> As a work around I've downloaded the latest 1.0.2 firewall module from puppetforge backed up the broken module in the installer module directory copied the 1.0.2 version into the modules directory renamed it (yes this is probably a very bad thing !) to 1.0.0 which the installer expects and re-run the install and presto the install completes.
>
> You maybe able to hack the installer script to use the 1.0.2 file name but I'm working on a test box so a quick and dirty hack with the file name did the job for me.
>
> Cheers

Paul,

As I discovered later, you don't even need to rename the module. The installer reads the <installer_root>/modules/install_modules.txt file to get the module names that it should install, but the file doesn't include version information. Just drop your updated module into the same folder and either move the old one out or rename it by prepending some text to it so that "puppetlabs-firewall*" doesn't match it, e.g. "DISABLED-puppetlabs-firewall-1.0.0.tar.gz".

--
Peter Bukowinski