-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
same problem for me.. I've notice the problem on modules using
autoloading...
I think I will stick to version 2.6.9...
can you at least file a detailed bug report? Thanks! Otherwise the
situation can't be really improved...
~pete
-BEGIN PGP
done!
http://projects.puppetlabs.com/issues/8433
Gus
On Fri, Jul 15, 2011 at 7:59 AM, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
same problem for me.. I've notice the problem on modules using
autoloading...
I think I will stick to version
I think the way I posted the contents of the modules may have been
misleading, as I do actually have each class in it's own file so
kvm::host class has it's own host.pp file. So far I've actually
noticed this problem only on my modules that make use of the
autoloading, so each class in it's own
Hi Trey,
same problem for me.. I've notice the problem on modules using
autoloading...
I think I will stick to version 2.6.9...
Gus
On Thu, Jul 14, 2011 at 8:57 AM, treydock treyd...@gmail.com wrote:
I think the way I posted the contents of the modules may have been
misleading, as I do
On Wed, Jul 13, 2011 at 2:26 PM, Gus gustavosoa...@gmail.com wrote:
Hi!
I've also noticed this (weird) behaviour. I am planning an (huge)
upgrade (from 0.25.x to 2.7.1) in all my puppet's boxes...
I've installed puppet's 2.7.1 gem and got a lot of Could not find
class problem... and
Hi Nigel,
here we go...
* all my classes are included (I was still using 0.25.x...)
* In my $confdir/manifests/classes/roles I have a very generic class for all
puppet hosts declared as follow:
class role_puppet_common {
$role = puppet_common
include common
include puppet::common
include
Hi!
I've also noticed this (weird) behaviour. I am planning an (huge)
upgrade (from 0.25.x to 2.7.1) in all my puppet's boxes...
I've installed puppet's 2.7.1 gem and got a lot of Could not find
class problem... and everything worked just fine with 0.25.x.
So, I decided to uninstall the gem for
