This repository was archived by the owner on Jun 11, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 11, 2019. It is now read-only.
Deployment with 'puppi' failed #4
Description
When 'install' is set to 'puppi', and everything else is left default, on my ubuntu server, /opt/activemq becomes a symlink to /opt and thus you can recurse though an infinite level of 'activemq' symlinks and puppet then fails to ensure the config file exists underneath that directory.
This is admittedly the first module I'm trying to install with puppi as opposed to via system packages, because I don't like the way Debian/Ubuntu packages activemq. However puppi is enabled and I haven't had any other errors with it.
Any ideas why this would be? I haven't had time to dig into the module code yet to know whether it's something in activemq or in puppi.
Activity
alvagante commentedon Oct 14, 2013
Don't use puppi for installation of modules applications, even if it's an available option it's rarey tested. Use the "source" install method, eventually.
You can use puppi for normal applications deployments, just it's not much tested the automated puppi installation of modules applications.
The issu is probably due to incorrect management of the downloaded tarball and the directory it contains.
ReplicaObscura commentedon Oct 14, 2013
Gotcha--thanks for the heads up. It seems to work fine with 'source'
Out of curiosity why is 'puppi' an option for module applications? Is it just because it's part of the example42 next-gen template?
Thanks again!
alvagante commentedon Oct 14, 2013
Yes, it's a setup that is cloned from module to module (where's is allowed installation from upstream source).
It' should create a the configs to run "puppi deploy activemq" and try to execute it during puppet run time.
But it's hardly useful and, as I told you, rarely used / tested.
The big is there anyway, so I leave the ticket open, even if I don't know when I'll look at it.