During routine backup/restore procedures from a Chef Infra Server which has the push-jobs add-on installed you may observe the following error during the restoration process:
Warning: opscode-push-jobs-server @ version not installed
This will result in the likely failure of the restoration of the instance as durning the reconfiguration of the software push-jobs will attempt to install before the nginx service is configured. The restoration run will subsequently fail at:
[2020-09-17T23:50:40-04:00] INFO: Processing runit_service[nginx] action restart (opscode-pushy-server::nginx line 29)
|Chef Infra Server||12.x +||Standalone|
|Chef Backend||2.x +||Cluster|
If you are considering push-jobs at the time of writing (September 2020) you should be aware that push-jobs is deprecated and soon to be EOL as per this product matrix https://docs.chef.io/versions/#deprecated-products-and-versions.
If you are already dependent on push-jobs we suggest you migrate away from this mechanism and instead consume a supportable pattern such as policyfiles or chef-run. Reach out to a Chef Engineer to discuss how to migrate away from push-jobs and what would be best suited for your deployment.
either a `chef-server-ctl status`
run: opscode-pushy-server: (pid 1098) 14415371s; run: log: (pid 1070) 14415371s
or `rpm -qa | grep push`
should reveal whether push-jobs is still installed on the existing host.
The best remedy is to uninstall push jobs on the current Infra Server Install. The official documentation to uninstall the server/client is here - https://docs.chef.io/uninstall/#chef-push-jobs.
To uninstall Push Jobs Server:
Then, follow up if needed with
chef-server-ctl stop opscode-pushy-server
rm -fr /opt/opscode/service/opscode-pushy-server
rm -fr /opt/opscode/sv/opscode-pushy-server
Uninstall the Push Jobs Server package using your OS, dpkg or rpm
rm -fr /opt/opscode-push-jobs-server
At this point, you should be able to reboot and not have the Push Jobs Server start the next time the system comes up.