Puppet 4.5.2


On Thursday, August 18, 2016 at 12:32:12 PM UTC-4, mike r wrote:
>
> Im trying to run an Nginx module, my install.pp has the following line
>
>
>
> $agent_version = $::puppetversion
>   
> #  if $agent_version < 3.8 {
> #    fail("---- Node ${::fqdn} has a Puppet agent version: 
> ${agent_version} which is not compatible with this modul    e. Need to have 
> minimum Puppet agent 3.8 -----")
>  # }
>  
> the IF statement is commented out, yet when I run agent on target, it 
> looks like its cached the old version of the manifest, it still tries to do 
> the IF statement
>
> [root@centos7node state]# puppet agent -t
> Info: Using configured environment 'production'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Evaluation Error: Error while evaluating a Resource Statement, Evaluation 
> Error: *Error while evaluating a Function Call, ---- Node centos7node has 
> a Puppet agent version: 4.5.2 which is not compatible with this module. 
> Need to have minimum Puppet agent 3.8 ----- at 
> /etc/puppetlabs/code/environments/production/modules/nginx/manifests/install.pp:18:3
>  
> on node centos7node*
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
>
>
> Not sure where the caching is occuring, on Master or Agent, Im guessing on 
> master. Any way to clear the cache on both ends? Didnt see anything in 
> docs. 
>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0d078221-7c0d-41b6-bf01-61dd46b76a84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to