Ensure procps-ng is installed on Red Hat.

[Tamerz]

The module expects the ps utility to already be installed, but it may not be.

# puppet apply mymanifest.pp 
Notice: Compiled catalog for 933b1f81aa39 in environment production in 0.03 seconds
Notice: /Stage[main]/Tftp::Install/Package[tftp-server]/ensure: created
Notice: /Stage[main]/Tftp::Install/Package[syslinux]/ensure: created
Error: /Stage[main]/Tftp::Service/Service[tftp.socket]: Could not evaluate: Execution of 'ps -ef' returned 1: Error: Could not execute posix command: No such file or directory - ps
Error: /Stage[main]/Tftp::Service/Service[tftp.socket]: Failed to call refresh: Execution of 'ps -ef' returned 1: Error: Could not execute posix command: No such file or directory - ps
Error: /Stage[main]/Tftp::Service/Service[tftp.socket]: Execution of 'ps -ef' returned 1: Error: Could not execute posix command: No such file or directory - ps
Notice: Applied catalog in 46.46 seconds

This adds an optional_packages parameter to install and adds procps-ng to the RedHat.yaml Hiera data.

[evgeni]

But… This module doesn't use ps anywhere. Is that a packaging bug in RHEL?

[Tamerz]

That is a good point. I tried on a different machine and purposely removed procps-ng and this module worked as expected. I'll remove this pull request since it seems to be something specific to machines I was testing on.

[evgeni]

I've hit similar things in the past. A lot of packages in RHEL assume presence of base packages (as they are in the @base group), but don't declare a dependency on them. So a normal VM installation works fine, but in a container without base things fail or behave differently.