Also, what version of puppetboard is being used?
On Jul 21, 2014 9:42 AM, "Ken Barber" wrote:
> Are we even sure this is a PuppetDB problem? And not an issue with the
> Dashboard itself? As I've shown, the report gets stored in PuppetDB as
> a failure. Having said that, if there is an issue in th
Are we even sure this is a PuppetDB problem? And not an issue with the
Dashboard itself? As I've shown, the report gets stored in PuppetDB as
a failure. Having said that, if there is an issue in the summary of
the report we don't store those stats ourselves in PuppetDB.
Maxim, I'd do the test I pr
Which version of puppedb are you running? If I'm not wrong, from puppetdb
2.1 catalog compilation errors are stored , but not for previous versions.
Regards,
El 21/07/2014 17:17, "Maxim Nikolaev" escribió:
> No. I haven't this feature.
> my puppet.conf looks like this:
>
> [main]
> modules = /et
No. I haven't this feature.
my puppet.conf looks like this:
[main]
modules = /etc/puppet/modules
hiera_config = /etc/puppet/hiera.yaml
pluginsync= true
server = HOSTNAME
#port = 8081
[agent]
server = HOSTNAME
report = true
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
[ma
Hi Maxim,
This is not directly reproducible by myself today:
https://gist.github.com/kbarber/c6941099bea07096361e ...
Perhaps something in your puppet.conf is doing this, I could imagine
something like:
usecacheonfailure = true
Causing this to happen, but I can't reproduce the exact same condit
Hi
I'm using Puppet with Dashboard and PuppetDB and Puppetdb board. I can see
all nodes and rfeports.
Problem is that when puppet fail to run on instance - i get report
"unchanged" instead of "fail".
For ex. I've changed postfix manifest to install package postfix1. Puppet
failed to run:
Erro
