Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix circuler dependency #657

Closed
wants to merge 3 commits into from
Closed

fix circuler dependency #657

wants to merge 3 commits into from

Conversation

b4ldr
Copy link
Member

@b4ldr b4ldr commented Jul 3, 2015

See issue #656

@3flex
Copy link
Contributor

3flex commented Jul 8, 2015

Did you test this on FreeBSD?

I'm not sure how this would solve the issue. nginx::config is a dependency of nginx::service so the service shouldn't start before the config is in place, including the creation of the log directory. While nginx::package also notifies nginx::service, the service start/restart won't happen until all dependencies have been resolved, including nginx::config.

It may be that the error log is being created in the wrong location in FreeBSD.

@3flex 3flex added the needs-feedback Further information is requested label Jul 8, 2015
@b4ldr
Copy link
Member Author

b4ldr commented Jul 10, 2015

Yes i did test this in freebsd as soon as i applied the patch the policy ran without error. You say that nginx::config is a dependency of nginx::service however it is not. nginx::config is set to notify nginx::service it does not require it and therefore there is not guaranteed to run before nginx::config. however nginx::config does require nginx::package which means everything in nginx::package including the notify to nginx::service needs to apply before nginx::config.

At least that is my understanding of how the dependency resolution works. Regardless without this patch nginx fails to run on a fresh freeBSD 10.1, with the patch t runs without issue

@3flex
Copy link
Contributor

3flex commented Jul 10, 2015

In Puppet when one resource notifies another, it still applies the standard ordering rules. Since nginx::config notifies nginx::service, all the resources in nginx::config will be applied before nginx::service.

While the patch might fix things in your environment I'm concerned about changing this behaviour as it may have unintended consequences on other platforms. We had a problem on DragonflyBSD/FreeBSD (#619) and I thought #635 might have solved it, but that might not be the case.

I'd like to know what the root cause is before applying any change and I'm not sure we know what that is yet.

@b4ldr
Copy link
Member Author

b4ldr commented Jul 15, 2015

ok no problem, ill try and set up a vagrant image to better troubleshoot the issue however im away at conferences for the next two weeks so it might take a while

@3flex
Copy link
Contributor

3flex commented Feb 3, 2016

Closing for now. If we get more information we can reopen. Thanks!

@3flex 3flex closed this Feb 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-feedback Further information is requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants