The resource for sentry.conf is defined in init.pp. It is not explicitly declared as a dependency for any of the setup tasks performed in install.pp, which may permit the catalog to try to execute those tasks before the file is created. This is wrong.
Everything that install.pp needs should be handled in advance of invoking that class. I propose a setup.pp class that ensures that the Sentry user and group are managed, as well as the target installation directory. Then the sentry.conf file resource can depend on setup.pp and finally install.pp can depend on the configuration file.
The resource for
sentry.confis defined ininit.pp. It is not explicitly declared as a dependency for any of the setup tasks performed ininstall.pp, which may permit the catalog to try to execute those tasks before the file is created. This is wrong.Everything that
install.ppneeds should be handled in advance of invoking that class. I propose asetup.ppclass that ensures that the Sentry user and group are managed, as well as the target installation directory. Then thesentry.conffile resource can depend onsetup.ppand finallyinstall.ppcan depend on the configuration file.