JDK server upgrades cause unexpected /bin/cat errors to appear on agents #2900
Description
Steps to Reproduce
- Rocky 9 puppetserver, downgrade to 'not-the-latest' java-17-openjdk-headless package, spin up OSP puppetserver
- agent nodes (various Linux flavors, mostly CentOS7 through Rocky9) established and happy
- dnf upgrade java-17-openjdk-headless on the puppetserver node, do not take any extraordinary action to restart puppetserver (it won't notice on its own).
- do agent runs against the puppetserver
Describe the Bug
Agent nodes begin showing:
Notice: Catalog compiled by [puppetserver-compiler.name]
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Exception while executing '/bin/cat': Cannot run program "/bin/cat" (in directory "."): error=2, No such file or directory on node [node.name]
Expected Behavior
"No unexplained errors" would be desirable. Whether that's "no error appears on the agent" or "a less dire one appears on the agent" or "puppetserver can detect an underlying change happened and deal with it or whine for a restart" or "explicit 'yodawg, gotta restart puppetserver'" docs/instructions somewhere, I leave up to the implementor.
Environment
- Puppet 8 agents and server
- Rocky 9 server, Rocky 8-9 agents