Is agent 3.2.2 too old(!) to run against server 2.4 (puppet v4) ?
got a brand new v4 server and clean v3 client; ran a basic test and got
puppetserver version: 2.4.0 puppet --version 3.2.2
(Test run on client node)
puppet agent -t --noop Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate: Error 500 on SERVER: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 500 </title> </head> <body> <h2>HTTP ERROR: 500</h2> <p>Problem accessing /prod/file_metadatas/plugins. Reason: <pre> No implementation of method: :form-encode* of protocol: #'ring.util.codec/FormEncodeable found for class: nil</pre></p> <hr /><i><small>Powered by Jetty://</small></i> </body> </html> Info: Loading facts in /var/lib/puppet/lib/facter/hbafacts.rb Info: Loading facts in /var/lib/puppet/lib/facter/default_gateway.rb Info: Loading facts in /var/lib/puppet/lib/facter/packages.rb Info: Loading facts in /var/lib/puppet/lib/facter/foreman.rb Info: Loading facts in /var/lib/puppet/lib/facter/disk_facts.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/macaddress.rb Info: Loading facts in /var/lib/puppet/lib/facter/manufacturer.rb Info: Loading facts in /var/lib/puppet/lib/facter/raid_ctrl.rb Info: Loading facts in /var/lib/puppet/lib/facter/tmx_vlan.rb Info: Loading facts in /var/lib/puppet/lib/facter/multipath.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/ipaddress.rb Info: Loading facts in /var/lib/puppet/lib/facter/tmx_name.rb Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: No format match the given format name or mime-type (b64_zlib_yaml) Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not send report: Error 400 on SERVER: YAML in network requests is not supported. See http://links.puppetlabs.com/deprecate_yaml_on_network
I've done a lot of googling but found no (other) solns.
We'd prefer to hang on to our current server v3.2.2 (& nodes v3.2.2) whilst we gradually move to server 2.4 (v4) and make the modules/manifests etc work against both versions until we have made everything v4 clean.
This because we have a lot of node types/modules and a big bang approach is one we want to avoid
Does the above mean I'm going to have to upgrade our current systems to eg v3.8 anyway?
Thanks a lot
Ok so it looks like upgrading the agent is (prob) the only way. What's the recommended method, to either 3.3 or even 3.8.?
There's lots of stuff on upgrades from 3 to 4, not so much on eg 3.2 to 3.3 or 3.8.