... | @@ -2,14 +2,6 @@ |
... | @@ -2,14 +2,6 @@ |
|
|
|
|
|
You can see all Kea issues with the `bug` label at [this link](https://gitlab.isc.org/isc-projects/kea/issues?label_name[]=bug). The following is a list of some of the more significant known issues in current and previous versions of Kea.
|
|
You can see all Kea issues with the `bug` label at [this link](https://gitlab.isc.org/isc-projects/kea/issues?label_name[]=bug). The following is a list of some of the more significant known issues in current and previous versions of Kea.
|
|
|
|
|
|
## Kea master
|
|
|
|
|
|
|
|
* Specific MariaDB versions have some issues when Kea is used with Galera clustering. See [this comment](https://gitlab.isc.org/isc-projects/kea/-/issues/1411#note_201946) for detailed info.
|
|
|
|
|
|
|
|
* When interface re-detection is enabled and an incorrect configuration is loaded (for instance, because it uses a disappearing interface in a subnet definition), the load fails and leaves the interface sockets closed.
|
|
|
|
|
|
|
|
* Some unit tests fail when using MySQL's September 19, 2020 release, version 8.0.22. This is under investigation in #1570.
|
|
|
|
|
|
|
|
## Kea 2.3.0
|
|
## Kea 2.3.0
|
|
|
|
|
|
* Lease allocation fails if Kea uses a recently released MariaDB 10.9.2. Our understanding is that this is a DB issue and a bug was reported: https://jira.mariadb.org/browse/MDEV-29381. Current recommendation is to not use this MariaDB version with Kea.
|
|
* Lease allocation fails if Kea uses a recently released MariaDB 10.9.2. Our understanding is that this is a DB issue and a bug was reported: https://jira.mariadb.org/browse/MDEV-29381. Current recommendation is to not use this MariaDB version with Kea.
|
... | @@ -50,7 +42,7 @@ DELETE FROM dhcp6_options WHERE scope_id = 2 AND dhcp_client_class NOT IN (SELEC |
... | @@ -50,7 +42,7 @@ DELETE FROM dhcp6_options WHERE scope_id = 2 AND dhcp_client_class NOT IN (SELEC |
|
|
|
|
|
## Kea 1.9.4
|
|
## Kea 1.9.4
|
|
|
|
|
|
* The ``kea-admin`` command may fail to upgrade database schema due to missing execute permission on the upgrade scripts. This can be fixed by setting the execute flag. e.g.
|
|
* The `kea-admin` command may fail to upgrade database schema due to missing execute permission on the upgrade scripts. This can be fixed by setting the execute flag. e.g.
|
|
|
|
|
|
```sh
|
|
```sh
|
|
$ chmod u+x {prefix}/share/kea/scripts/mysql/*.sh
|
|
$ chmod u+x {prefix}/share/kea/scripts/mysql/*.sh
|
... | @@ -100,9 +92,9 @@ $ mysql -u DBUSER -p DBNAME < kea1.9.4-schema-fix.mysql |
... | @@ -100,9 +92,9 @@ $ mysql -u DBUSER -p DBNAME < kea1.9.4-schema-fix.mysql |
|
|
|
|
|
* There is a problem establishing a MySQL cluster backend with Kea 1.6. See issue [#901] (https://gitlab.isc.org/isc-projects/kea/issues/901)
|
|
* There is a problem establishing a MySQL cluster backend with Kea 1.6. See issue [#901] (https://gitlab.isc.org/isc-projects/kea/issues/901)
|
|
|
|
|
|
* MySQL 8.0.17 introduced more restrictive access model, where creating procedures requires additional privileges. If using this or later versions of MySQL, make sure the user running ``kea-admin db-upgrade`` command has sufficient privileges.
|
|
* MySQL 8.0.17 introduced more restrictive access model, where creating procedures requires additional privileges. If using this or later versions of MySQL, make sure the user running `kea-admin db-upgrade` command has sufficient privileges.
|
|
|
|
|
|
* Command ``remote-option-def6-set`` was reported to fail sporadically on Debian 10 giving an error similar to this: "Prepared statement needs to be re-prepared". This is a MySQL configuration issue and can be corrected by tweaking the following parameters in your my.cnf file:
|
|
* Command `remote-option-def6-set` was reported to fail sporadically on Debian 10 giving an error similar to this: "Prepared statement needs to be re-prepared". This is a MySQL configuration issue and can be corrected by tweaking the following parameters in your my.cnf file:
|
|
|
|
|
|
```
|
|
```
|
|
table_open_cache 128=>16384
|
|
table_open_cache 128=>16384
|
... | @@ -140,7 +132,6 @@ Significant known issues include: |
... | @@ -140,7 +132,6 @@ Significant known issues include: |
|
* Problems with MariaDB: https://gitlab.isc.org/isc-projects/kea/issues/53
|
|
* Problems with MariaDB: https://gitlab.isc.org/isc-projects/kea/issues/53
|
|
* Reported memory leak with the RADIUS hook library: https://gitlab.isc.org/isc-projects/kea/issues/87
|
|
* Reported memory leak with the RADIUS hook library: https://gitlab.isc.org/isc-projects/kea/issues/87
|
|
|
|
|
|
|
|
|
|
## Kea 1.4.0
|
|
## Kea 1.4.0
|
|
|
|
|
|
* A new High Availability feature introduces a mechanism to synchronize leases between partners. If there is a large (on the order of hundreds of thousands) number of leases to by synced, the amount of time it takes for the server to fully transmit the database may be higher than then timeout. As a result, an attempt to sync large database may timeout even though the partner is alive and responding. This limitation can be worked around by changing the timeout values in src/lib/config/timeouts.h and recompiling. This is addressed with paged updates, added in Kea1.5Beta1.
|
|
* A new High Availability feature introduces a mechanism to synchronize leases between partners. If there is a large (on the order of hundreds of thousands) number of leases to by synced, the amount of time it takes for the server to fully transmit the database may be higher than then timeout. As a result, an attempt to sync large database may timeout even though the partner is alive and responding. This limitation can be worked around by changing the timeout values in src/lib/config/timeouts.h and recompiling. This is addressed with paged updates, added in Kea1.5Beta1.
|
... | @@ -156,8 +147,6 @@ Significant known issues include: |
... | @@ -156,8 +147,6 @@ Significant known issues include: |
|
## Kea 1.4.0-beta
|
|
## Kea 1.4.0-beta
|
|
* The Kea configuration example file for High Availability (doc/examples/kea4/ha-load-balancing-primary.json) includes extraneous comma signs at the end of lines 56 and 218. This causes the server to reject this configuration and consequently the server fails to start. Removing the culprit comma signs from this configuration resolves the problem.
|
|
* The Kea configuration example file for High Availability (doc/examples/kea4/ha-load-balancing-primary.json) includes extraneous comma signs at the end of lines 56 and 218. This causes the server to reject this configuration and consequently the server fails to start. Removing the culprit comma signs from this configuration resolves the problem.
|
|
|
|
|
|
## Kea 1.3.0
|
|
|
|
|
|
|
|
## Kea 1.2.0
|
|
## Kea 1.2.0
|
|
|
|
|
|
* Two scripts used to update databases schemes to newest versions {{{src/share/database/scripts/mysql/upgrade_5.0_to_5.1.sh}}} and {{{src/share/database/scripts/pgsql/upgrade_3.0_to_3.1.sh}}} are not installed during the installation process. They should be manually copied from the tarball to {{{{kea_installation_directory}/share/kea/scripts/mysql}}} and {{{{kea_installation_directory}/share/kea/scripts/pgsql}}}
|
|
* Two scripts used to update databases schemes to newest versions {{{src/share/database/scripts/mysql/upgrade_5.0_to_5.1.sh}}} and {{{src/share/database/scripts/pgsql/upgrade_3.0_to_3.1.sh}}} are not installed during the installation process. They should be manually copied from the tarball to {{{{kea_installation_directory}/share/kea/scripts/mysql}}} and {{{{kea_installation_directory}/share/kea/scripts/pgsql}}}
|
... | @@ -190,7 +179,6 @@ Significant known issues include: |
... | @@ -190,7 +179,6 @@ Significant known issues include: |
|
|
|
|
|
* Compilation on Ubuntu 15.10 x64 with gcc-4.9 fails. The reason is to be investigated (#4244).
|
|
* Compilation on Ubuntu 15.10 x64 with gcc-4.9 fails. The reason is to be investigated (#4244).
|
|
|
|
|
|
|
|
|
|
## Kea 1.0.0-beta, 1.0.0 (final)
|
|
## Kea 1.0.0-beta, 1.0.0 (final)
|
|
|
|
|
|
* Kea doesn't handle missing hooks libraries information correctly during the reconfiguration process. If Kea has one or more hooks libraries loaded and the hooks-libraries element is removed from the configuration file, a reconfiguration will not unload the libraries. The workaround is to keep the hooks-libraries element in the configuration file, but specify it as an empty list, i.e. {{{"hooks-libraries": [{ }] }}}. (See ticket #3998.)
|
|
* Kea doesn't handle missing hooks libraries information correctly during the reconfiguration process. If Kea has one or more hooks libraries loaded and the hooks-libraries element is removed from the configuration file, a reconfiguration will not unload the libraries. The workaround is to keep the hooks-libraries element in the configuration file, but specify it as an empty list, i.e. {{{"hooks-libraries": [{ }] }}}. (See ticket #3998.)
|
... | @@ -255,6 +243,7 @@ Significant known issues include: |
... | @@ -255,6 +243,7 @@ Significant known issues include: |
|
|
|
|
|
* Configuration option --disable-rpath is not working. Binaries always have hard coded RPATH value. Seee #3738 for details.
|
|
* Configuration option --disable-rpath is not working. Binaries always have hard coded RPATH value. Seee #3738 for details.
|
|
|
|
|
|
|
|
|
|
## Kea 0.9.1 beta1
|
|
## Kea 0.9.1 beta1
|
|
|
|
|
|
* The JSON-based configuration file needs to be updated when migrating from 0.9
|
|
* The JSON-based configuration file needs to be updated when migrating from 0.9
|
... | @@ -301,8 +290,8 @@ For DHCPv4 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp4- |
... | @@ -301,8 +290,8 @@ For DHCPv4 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp4- |
|
|
|
|
|
For DHCPv6 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp6-limit.
|
|
For DHCPv6 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp6-limit.
|
|
|
|
|
|
|
|
|
|
## Kea 0.9 beta1
|
|
## Kea 0.9 beta1
|
|
|
|
|
|
This version of Kea is a first stand-alone (without BIND10 framework) release.
|
|
This version of Kea is a first stand-alone (without BIND10 framework) release.
|
|
|
|
|
|
* Before upgrading from Kea 0.8, make sure you understand that configuration has changed (bindctl is no longer used, and configuration is stored in JSON files).
|
|
* Before upgrading from Kea 0.8, make sure you understand that configuration has changed (bindctl is no longer used, and configuration is stored in JSON files).
|
... | @@ -320,6 +309,7 @@ For DHCPv4 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp4- |
... | @@ -320,6 +309,7 @@ For DHCPv4 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp4- |
|
For DHCPv6 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp6-limit.
|
|
For DHCPv6 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp6-limit.
|
|
|
|
|
|
## Kea 0.8 (BIND10 1.2.0)
|
|
## Kea 0.8 (BIND10 1.2.0)
|
|
|
|
|
|
The version of Kea 0.8 included in BIND 1.2.0 is an engineering snapshot and intended for experimental use only. The current list of known defects in Kea can be found [http://kea.isc.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&subproject=DHCP&type=defect&col=id&col=summary&col=type&col=priority&col=component&col=time&order=id here].
|
|
The version of Kea 0.8 included in BIND 1.2.0 is an engineering snapshot and intended for experimental use only. The current list of known defects in Kea can be found [http://kea.isc.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&subproject=DHCP&type=defect&col=id&col=summary&col=type&col=priority&col=component&col=time&order=id here].
|
|
|
|
|
|
Significant known issues with the DHCP servers in this release are:
|
|
Significant known issues with the DHCP servers in this release are:
|
... | | ... | |