no manifestmodules after puppet-agent v7->v8 update

[Todd Porter]

I've been urnning puppetserver v8 for a few months with all the agents still on v7. I just updated a few test nodes from agent v7 to v8 and no manifest/modules are being applied to the client now. I know the client is pulling the correct env from running `puppet agent -t -d | tee -a /tmp/puppet_output.txt` and seeing this entry on the log:
"Debug: HTTP POST https://puppetserver:8140/puppet/v3/catalog/nodename.example.com?environment=testenv returned 200 OK"
I only made 1 chnage to the textenv environment because of initial error in log with main init.pp file:

$nodehostname = $facts['hostname']
-to-
$nodehostname = $facts['networking']['hostname']

There are no errors in the client log now. It is connecting to master but pulling an empty catalog

[Tim Mooney]

In regard to: [Puppet Users] no manifestmodules after puppet-agent v7->v8...:

It's when the clients get upgraded to v8 that they stop supplying the
list of facts on the v8 deprecated facts list (which isn't complete).

https://help.puppet.com/core/8/Content/PuppetCore/upgrading-from-puppet7-to-puppet8.htm

If you add

include_legacy_facts=true

in puppet.conf (not sure, but I think [agent] section) on a client
system and the problem goes away, then it's code somewhere that is still
depending on legacy facts.

I thought I had done a good job converting my site to modern facts before
the v8 upgrade, but I found quite a few places I missed, especially some
old/large ERB templates.

You may also find useful info in your puppetserver.log

Good luck,

Tim
--
Tim Mooney Tim.M...@ndsu.edu
Enterprise Computing & Infrastructure /
Division of Information Technology / 701-231-1076 (Voice)
North Dakota State University, Fargo, ND 58105-5164