Some resources not applied on first run

[Guy Knights]

I've noticed from time to time, and with certain manifests, that sometimes there are resources that won't be applied on first run. There's no errors during the initial run to say that a dependency failed, the resource just isn't applied. If I then run puppet again after the first run, the resource seems to then be applied ok.

Does anyone know why this might happen? As I said, it's only an occasional occurrence, and only with some manifests.

Thanks,

Guy

[jcbollinger]

On Friday, November 8, 2013 1:53:28 PM UTC-6, Guy Knights wrote:

I've noticed from time to time, and with certain manifests, that sometimes there are resources that won't be applied on first run. There's no errors during the initial run to say that a dependency failed, the resource just isn't applied. If I then run puppet again after the first run, the resource seems to then be applied ok.

Does anyone know why this might happen? As I said, it's only an occasional occurrence, and only with some manifests.

If a resource is not applied, and there is no error message indicating that it or one of its dependencies failed, then either that resource is already in sync or it is not in the catalog at all.  Running the agent in --debug mode should allow you to distinguish those alternatives.

Do note, however, that "one of its dependencies failed" includes not just related resources, but also the requirements of the resource's provider.  Most providers depend on external programs, and Puppet will check for their existence when trying to choose providers for all the resources in the catalog, before applying any resources.  It cannot apply a resource for which there is no applicable provider, but if the binaries required by some provider are installed by Puppet then that provider will be available during the next Puppet run.


John