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

CentOS Stream 8/pdns 4.3.1 tasks/database-mysql gets schema location wrong #92

Closed
dlcarmean opened this issue Dec 1, 2020 · 3 comments · Fixed by #100
Closed

CentOS Stream 8/pdns 4.3.1 tasks/database-mysql gets schema location wrong #92

dlcarmean opened this issue Dec 1, 2020 · 3 comments · Fixed by #100

Comments

@dlcarmean
Copy link

On the below-described system, the role tries to load schema.mysql.sql from /usr/share/doc/pdns-backend-mysql/, but the pdns-backend-mysql RPM places it in /usr/share/doc/pdns/

$ rpm -ql pdns-backend-mysql | grep '/schema.mysql.sql'
/usr/share/doc/pdns/schema.mysql.sql

$ rpm -qa | grep pdns
pdns-4.3.1-1.el8.x86_64
pdns-backend-mysql-4.3.1-1.el8.x86_64

$ uname -a
Linux vm1-dns.lax.... 4.18.0-240.el8.x86_64 #1 SMP Fri Sep 25 19:48:47 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/redhat-release
CentOS Stream release 8

@pieterlexis
Copy link
Contributor

pieterlexis commented Dec 1, 2020

What repo does this package come from? PowerDNS or EPEL?

nvm, EPEL by the look of it

@dlcarmean
Copy link
Author

dlcarmean commented Dec 1, 2020

Yes, EPEL. The only vars I set to run the playbook/role were the db credentials. I have not checked other version combos/repos/builds.

@pieterlexis
Copy link
Contributor

so it looks like EPEL ships the file in a different directory than PowerDNS does. A work-around here is using

pdns_install_repo: "{{ pdns_auth_powerdns_repo_43 }}"

We'll need to find a way to detect this case. I've tried with with_first_found, but that does not seem to work on files on the target.

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

Successfully merging a pull request may close this issue.

2 participants