I ended up moving storeconfigs=true and storeconfigs_backend=puppetdb to
the [main] section in /etc/puppet/puppet.conf. No idea why that works as it
seems to contradict every piece of documentation and examples I've come
across. If I find time I'll try to figure out why this is.
Thanks,
Mikael
This is the error I got running puppetlab's puppetdb module trying to setup
puppetdb and postgresql. I was able to run it locally with puppet apply.
I am running puppet 3.5.1 on both master and agent with hiera. Master is
running Apache+Passenger.
Has anyone encounter similar issue before and c
FACT-185 is the ticket I've been following for this issue. I haven't
upgraded my AWS instances that are EC2-VPC vs EC2-Classic. The classic
works, but VPC has been failing due to the fact that the EC2 fact
depends on a constant MAC address which is not the case in VPC
instances.
On 27.04.2014
I searched around about this but couldn't find if puppetlabs is working in
a fix or not.
facter running in AWS VPC doesn't show ec2 facts:
# facter --version
2.0.1
# facter -p virtual
xenhvm
# facter -p | grep ec2
Returns nothing.
Thanks,
Felipe
--
You received this message because you are s
Hi everyone,
thanks all for your answers but i'm starting to think that there is way to
pass puppet "undef" value from a rspec test...
If anybody has the solution to fix this test suite (
https://github.com/riton/puppetrspec) please tell me; otherwise I'll have
to rewrite my manifests and replace
I made a module called resource_factory:
https://forge.puppetlabs.com/jaydub/resource_factory
It has two parts. One is the resource_factory class, the other is the
defined_resource_factory resource type. They both do the same kind of thing
— wrap around create_resources with a hiera look up on
