Bug 2186505
| Summary: | Upgrade from pdns-backend-sqlite-4.6.2 to pdns-backend-sqlite-4.7.3 left server unable to start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | David Anderson <fedora-packaging2> |
| Component: | pdns | Assignee: | Morten Stevens <mstevens> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel8 | CC: | mstevens, ruben, sander |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-05 14:08:12 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
David Anderson
2023-04-13 14:28:32 UTC
The mandatory schema update - https://raw.githubusercontent.com/PowerDNS/pdns/master/modules/gsqlite3backend/4.3.1_to_4.7.0_schema.sqlite3.sql - adds the column which is given as missing in the above error message, plus another column and an index. This issue was experienced by me with the SQLite back-end, but will exist with other SQL back-ends too. So far, we haven't received any reports of issues after upgrading from version 4.6 to 4.7. A database upgrade is required, but the service should still run even without the database upgrade. In our tests, PowerDNS ran without issues after upgrading to version 4.7.x, even without the database upgrade. We tested it with PostgreSQL, MySQL, and SQLite as the database backends. I apologize for the problems you encountered during the upgrade. Due to various reasons, as a packager maintainer, we are not allowed to make changes to other components such as the database. Therefore, the database upgrade needs to be performed by you. Since this is not a bug, I'm closing the ticket. Furthermore, I would like to provide you with some information regarding the upgrade. PowerDNS 4.6 will soon reach its end of life (EOL). Please see: https://doc.powerdns.com/authoritative/appendices/EOL.html. RHEL 8 and RHEL 9 will be supported until 2029 and 2032. Therefore, it is necessary for us to upgrade to newer versions in order to ensure the availability of appropriate bug fixes and security updates. Maybe it could be a feature request to the PowerDNS developers to have PowerDNS itself automatically perform the database upgrade. |