| {cWhen running a simple apply block on a Windows host i'm getting the following error:
[WSMAN ERROR CODE: 2152992672]: <f:WSManFault Code='2152992672' Machine='windows.domain.tld' xmlns:f='http://schemas.microsoft.com/wbem/wsman/1/wsmanfault'><f:Message><f:ProviderFault path='C:\Windows\system32\pwrshplugin.dll' provider='microsoft.powershell'>The current deserialized object size of the data received from the remote client computer exceeded the allowed maximum object size. The current deserialized object size is 10714116. The allowed maximum object size is 10485760.</f:ProviderFault></f:Message></f:WSManFault>
|
The plan i'm running is fairly simple, it installs Puppet agent then is attempting to render our initial Puppet config template:
# Install Puppet Agent on a VM |
plan encore_rp::puppet_agent_install ( |
TargetSpec $nodes, |
String[1] $bolt_base_path, |
String[1] $puppet_master, |
String[1] $puppet_environment, |
) { |
$targets = get_targets($nodes) |
$os_family = $node_facts.first['os']['family'] |
if $os_family == 'windows' { |
# windows install |
run_task('puppet_agent::install', $targets) |
$puppet_conf_path = 'C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf' |
} |
else { |
# linux install |
run_task('package::linux', $targets, |
name => 'puppet-agent', |
action => 'install') |
$puppet_conf_path = '/etc/puppetlabs/puppet/puppet.conf' |
} |
|
apply($targets) { |
file { $puppet_conf_path: |
ensure => file, |
content => template("${bolt_base_path}/encore_rp/templates/puppet/puppet.conf.erb"), |
} |
} |
} |
The template that we're using is pretty basic too:
I've tried the following:
- Removing every module in my modules/ directory so that pluginsync wasn't pushing stuff to the remote host, this didn't change the result
- Delete the cache on the node then try the plan again. This worked! I'm guessing because there was a bunch of old cache from different modules and when trying to apply our new catalog the apply block was returning results that were huge for all of the files it was removing in the logs.
I will try some more to get solid reproduction steps. I do have a feeling this has to do with pluginsync, out-dated cache and large changes that happen during the apply step. I'm guessing you could recreate this bug in a number of different ways by generating very large outputs (notifys) in an apply() block. |
