Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 511
    • Issues 511
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 56
    • Merge requests 56
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Wiki
  • known issues list

known issues list · Changes

Page history
add Kea 2.1.0 known issue authored Nov 18, 2021 by Andrei Pavel's avatar Andrei Pavel
Hide whitespace changes
Inline Side-by-side
known-issues-list.md
View page @ 0880f43c
......@@ -13,6 +13,16 @@ of MariaDB, attempts to create or update the database will fail with the error `
* Some unit tests fail when using MySQL's latest release as of September 19 versioned 8.0.22. This is under investigation in #1570.
## Kea 2.1.0
* The Kea documentation project hosted at https://kea.readthedocs.io/ started having build failures
in October. This was not a single occurrence and happened with multiple projects which is documented
[here](https://blog.readthedocs.com/build-errors-docutils-0-18/). It caught the release of 2.1.0 off
guard. This was fixed with #2161 in master, but to keep the `Kea-2.1.0` reflecting the released
sources, instead of moving it, `Kea-2.1.0-fix` was added. This is what the version that appears in
the Read the Docs sidebar and it should be interpreted as having `Kea-2.1.0` documentation.
In reality, it only has the documentation build fix on top.
## Kea 1.9.10 & 1.9.11
* If, using configuration backend on Kea 1.9.10 or 1.9.11, you managed to add a client class with associated option data, and then removed the client class, you would be left with dangling option data rows in the database. Option data rows are now properly removed when the associated client class is removed after #2094 which was released with 2.0.0. The foreign key constraint which helps realize the cascading delete will fail to be created on upgrade to the new schema with the following error:
......
Clone repository

🏠 Homepage

📖 Docs

📦 Download: sources, packages, git

🚚 Release notes

🛠 Hooks

🐛 Known issues (serious), all issues

🗒 Mailing lists: kea-users, kea-dev

🌍 Community developed Tools


Dev corner

  • designs

  • gitlab howto

  • coding guidelines

  • release process

  • Developer's guide


🔍 All wiki pages