Skip to content

No require for File: sites-enabled and sites-available folders #894

@ubellavance

Description

@ubellavance

Hi,

I think that this module lacks a set of require directives for the sites-enabled and sites-available folders. On ther first puppet run on a freshly installed VM, the puppet run doesn't complete if puppet choses to create the files before the directory.

Error: Could not set 'file' on ensure: No such file or directory - /etc/opt/rh/rh-nginx18/nginx/sites-available/atqtestssl.traceability.ca.conf20161003-4240-zx4832
Error: Could not set 'file' on ensure: No such file or directory - /etc/opt/rh/rh-nginx18/nginx/sites-available/atqtestssl.traceability.ca.conf20161003-4240-zx4832
Wrapped exception:
No such file or directory - /etc/opt/rh/rh-nginx18/nginx/sites-available/atqtestssl.traceability.ca.conf20161003-4240-zx4832
Error: /Stage[main]/Nginx/Nginx::Resource::Vhost[atqtestssl.traceability.ca]/Concat[/etc/opt/rh/rh-nginx18/nginx/sites-available/atqtestssl.traceability.ca.conf]/File[/etc/opt/rh/rh-nginx18/nginx/sites-available/atqtestssl.traceability.ca.conf]/ensure: change from absent to file failed: Could not set 'file' on ensure: No such file or directory - /etc/opt/rh/rh-nginx18/nginx/sites-available/test.example.com.conf20161003-4240-zx4832

Please note that I use non-standard folders location because I use the rh-nginx18 package from Red Hat Software Collections, but I think that the module shouldn't assume that the sites-available and sites-enabled folders exist.

If I run puppet a second time, it works OK.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions