-
-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong number of arguments given #194
Comments
Sure. Here is simplest ever config i've just tried, result the same. class { '::consul':
config_hash => {
'bootstrap_expect' => 1,
'client_addr' => '0.0.0.0',
'data_dir' => '/opt/consul',
'datacenter' => $datacenter,
'log_level' => 'INFO',
'node_name' => $::fqdn,
'server' => true,
'ui_dir' => '/opt/consul/ui'
}
} |
I see the problem. For some reason the function being used in your puppet run is https://github.com/solarkennedy/puppet-consul/blob/master/manifests/config.pp#L97 Can you tell me in your locally installed module whats files are in |
In
In
|
Well, that's even more strange then... |
HAHA but the error makes no sense: Error 400 on SERVER: sorted_json(): Wrong number of arguments given (3 for 1) Can you delete the entire module, restart your puppetmaster, ensure the module isin't being picked up, install module again, restart puppetmaster. I've come across similar issues in the past with functions. Since these functions run on puppet MASTER (not the individual agents/nodes) it caches them and causes weird issues until puppetmaster has been restarted. |
Oh, my excuses... Somehow puppet server cached old manifests (i always thinked it's impossible). After restarting apache all worked like a charm! Modules managed by r10k after hook from git repo, so i'm looking into modules on master rarely. PS: new module updated web_ui but didn't touched consul itself. |
Glad to see you got it resolved 👍 |
Hi there, I have the same issue and I can't get rid of cache!
Any ideas please? |
Pretty strange. @mrh666 can you look at |
solarkennedy, sure!
Check the config.pp:
On the instance:
I can't believe but it's cached somehow or ... |
solarkennedy, Just in case I deployed a new instance. Same story, it's cached on master:
|
@mrh666 did you restart the puppet master and try again? Puppet caches function eternally until a restart of the puppet master. |
@Split3, sure I did. And just in case I did it again:
I can see all the processes are running from the moment I restarted them 14:12 - 14:13:
And I still getting obsolete manifest on node:
Any idea how can I coerce Puppet Master to reset the cache? |
Hi, |
Can you please explain what this thing want from me? Used default config like:
The text was updated successfully, but these errors were encountered: