Hi Vince,

This sounds like an issue with the MODULE, could you please submit a ticket
at https://tickets.puppetlabs.com/browse/MODULES?

Thanks!
Morgan

On Thu, Aug 20, 2015 at 8:37 AM Vince Skahan <[email protected]> wrote:

> Is the official supported puppetlabs-splunk module 'not' future parser
> compatible ?
>
> Create a foo.pp containing:
>      class { 'splunk::forwarder': }
>
> Run puppet apply --noop with the future parser disabled - looks good...
>
> # puppet apply --noop foo.pp
> Notice: Compiled catalog for localhost.localdomain in environment
> production in 0.49 seconds
> Notice: /Stage[main]/Splunk::Forwarder/Package[splunkforwarder]/ensure:
> current_value absent, should be present (noop)
> Notice:
> /Stage[main]/Splunk::Forwarder/Splunkforwarder_input[default_host]/ensure:
> current_value absent, should be present (noop)
> Notice:
> /Stage[main]/Splunk::Forwarder/Splunkforwarder_output[tcpout_defaultgroup]/ensure:
> current_value absent, should be present (noop)
> Notice:
> /Stage[main]/Splunk::Forwarder/Splunkforwarder_output[defaultgroup_server]/ensure:
> current_value absent, should be present (noop)
> Notice:
> /Stage[main]/Splunk::Forwarder/Ini_setting[forwarder_splunkd_port]/ensure:
> current_value absent, should be present (noop)
> Notice: Class[Splunk::Forwarder]: Would have triggered 'refresh' from 5
> events
> Notice:
> /Stage[main]/Splunk::Platform::Posix/Exec[license_splunkforwarder]/returns:
> current_value notrun, should be 0 (noop)
> Notice: Class[Splunk::Platform::Posix]: Would have triggered 'refresh'
> from 1 events
> Notice: /Stage[main]/Splunk::Virtual/Service[splunk]/ensure: current_value
> stopped, should be running (noop)
> Notice: Class[Splunk::Virtual]: Would have triggered 'refresh' from 1
> events
> Notice: Stage[main]: Would have triggered 'refresh' from 3 events
> Notice: Finished catalog run in 0.31 seconds
>
> Run the same test specifying the future parser - total fail....
>
> # puppet apply --noop foo.pp --parser future
> Notice: Compiled catalog for localhost.dhcp4.washington.edu in
> environment production in 0.79 seconds
> Error: Could not find dependent Service[splunk] for
> Package[splunkforwarder] at
> /etc/puppetlabs/puppet/modules/splunk/manifests/forwarder.pp:76
>
> I'm running 3.8.2 here FWIW, but the same failure happens (more verbosely)
> on 2015.2
>
> Wondering if this might be related to
> https://tickets.puppetlabs.com/browse/PUP-4520 which was reportedly fixed
> according to the PUP.
>
> Thoughts ?  Bug in puppet or the module ?
> There's definitely a bug someplace....
>
> Should I report a bug to PL on this one ?  On the module, or the PE
> product itself ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/93a38d17-4b04-4706-b9f0-bb1529b8adbc%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/93a38d17-4b04-4706-b9f0-bb1529b8adbc%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Morgan Haskel
[email protected]
Module Engineer

*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Final Countdown discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-register-now-its-the-final-countdown-tickets-13115894995?discount=FinalCountdown>
*
*—**save $149!*

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv1id4TO6e2%3D8-DcqA699qRPSP8oJ5Dd_KR9SYo0jgpWqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to