Bug 1768258
Summary: | GeoIP2 feature is looking in wrong path | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michael Cronenworth <mike> |
Component: | bind | Assignee: | Petr Menšík <pemensik> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | anon.amish, mruprich, msehnout, pemensik, pzhukov, thozza, vonsch, zdohnal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | bind-9.11.13-2.fc31 bind-9.11.13-2.fc30 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-29 00:54:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael Cronenworth
2019-11-03 18:14:41 UTC
Thank you for the report. It has wrong default in bin/named/config.c, line 75. We did some directory customizations in default config file. But I think in this case, I would patch default inside binary. Anyway, it has easy workaround, just specify correct geoip-directory in options: options { # ... geoip-directory "/usr/share/GeoIP"; # ... }; Reported upstream: https://gitlab.isc.org/isc-projects/bind9/issues/1301 Thanks for your diligence, Petr. Merged upstream [1], and fix is built in rawhide. Added explicit geoip-directory into config file. https://gitlab.isc.org/isc-projects/bind9/merge_requests/2527/commits FEDORA-2019-c703d2304a has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c703d2304a FEDORA-2019-73a8737068 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-73a8737068 Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. This bug was accidentally closed due to a query error. Reopening. bind-9.11.13-2.fc31, bind-dyndb-ldap-11.2-2.fc31, dnsperf-2.3.2-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-73a8737068 bind-9.11.13-2.fc30, bind-dyndb-ldap-11.1-20.fc30, dhcp-4.3.6-38.fc30, dnsperf-2.3.2-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c703d2304a bind-9.11.13-2.fc31, bind-dyndb-ldap-11.2-2.fc31, dnsperf-2.3.2-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. bind-9.11.13-2.fc30, bind-dyndb-ldap-11.1-20.fc30, dhcp-4.3.6-38.fc30, dnsperf-2.3.2-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. |