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

should deploy config before installing package #11

Closed
Habbie opened this issue Jul 11, 2016 · 3 comments
Closed

should deploy config before installing package #11

Habbie opened this issue Jul 11, 2016 · 3 comments

Comments

@Habbie
Copy link
Member

Habbie commented Jul 11, 2016

I have both auth and recursor running on a machine, and the plan is to give them non-conflicting IP bindings. However, the recursor is installed (via apt-get in this case) before deploying the config, which means apt-get fails because the recursor is unable to bind to 127.0.0.1. If we deploy the config first I feel we could avoid some painful situations.

A similar consideration most likely applies to the auth role.

@atosatto
Copy link
Contributor

atosatto commented Sep 7, 2016

Hey @Habbie, I tried to find a workaround for your issue but unfortunately the recursor.conf.j2 template needs to know the pdns_recursor package version in order to properly serialize the given configuration (https://github.com/PowerDNS/pdns_recursor-ansible/blob/master/templates/recursor.conf.j2#L20)

Given the role use-cases, do you think this is actually an issue?
In that case we can try to refactor a little bit the role logic to workaround the pdns_recursor_version requirement in the configuration template.

@Habbie
Copy link
Member Author

Habbie commented Sep 8, 2016

I imagine that not many people will run into this the way I did, so perhaps it's not a huge priority. It depends on how hard that refactor would be :)

atosatto added a commit that referenced this issue Nov 9, 2016
@atosatto
Copy link
Contributor

atosatto commented Nov 9, 2016

Closing the issue since it has been solved by #19.

@atosatto atosatto closed this as completed Nov 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants