how to force an error

[Jose Luis Ledesma]

Hi,

   Does exist some way to force a  error while applying the catalog? We need to check some facts vs configuration and force an error if doesnt' match, so we could have a report from the node in the puppetdb with the failed state. (we cannot use a compilation/evaluation error because it doesn't report to the puppetdb)

  Currently we use this ugly workaround:

    exec {'dummy exec to force an error':

      path => ['/bin'],

    }

  Is there any better solution?

thanks,

 

[Ken Barber]

> Does exist some way to force a error while applying the catalog? We need
> to check some facts vs configuration and force an error if doesnt' match, so
> we could have a report from the node in the puppetdb with the failed state.
> (we cannot use a compilation/evaluation error because it doesn't report to
> the puppetdb)

This is fixed in the next release, 2.1.0.

> Currently we use this ugly workaround:
>
> exec {'dummy exec to force an error':
> path => ['/bin'],
> }
>
> Is there any better solution?

I know its vapourware until its released, but I'd wait for 2.1.0 and
use the fail function,

ken.

[jcbollinger]

Not really.  You could write a custom type that always fails, but that seems a lot of trouble, and not necessarily any better.  I'd write that exec a little prettier, though:

exec { 'Intentional Failure':
  command => '/bin/false'
}


John