|
# Known Issues in Kea
|
|
# Known Issues in Kea
|
|
|
|
|
|
You can see all Kea issues with `bug` label under [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 `bug` label under [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
|
|
## Kea master
|
|
|
|
|
|
* MariaDB is now the default MySQL server in some instances of Linux (e.g. Debian 9, Fedora 29). On some versions
|
|
* MariaDB is now the default MySQL server in some instances of Linux (e.g. Debian 9, Fedora 29). On some versions
|
|
of MariaDB, attempts to create or update the database will fail with the error `ERROR 1071 (42000) at line 805: Specified key was too long; max key length is 767 bytes`. The following ISC Knowledgebase article: https://kb.isc.org/docs/maria-10x-and-kea describes the issue and lists the MariaDB settings needed to overcome it.
|
|
of MariaDB, attempts to create or update the database will fail with the error `ERROR 1071 (42000) at line 805: Specified key was too long; max key length is 767 bytes`. The following ISC Knowledgebase article: https://kb.isc.org/docs/maria-10x-and-kea describes the issue and lists the MariaDB settings needed to overcome it.
|
... | @@ -76,7 +76,7 @@ tmp_table_size 32M=>64M |
... | @@ -76,7 +76,7 @@ tmp_table_size 32M=>64M |
|
join_buffer_size 256k=>512k
|
|
join_buffer_size 256k=>512k
|
|
```
|
|
```
|
|
|
|
|
|
For generic MySQL discussion about the problem, see https://bugs.mysql.com/bug.php?id=42041. For the specific Kea issue, see https://gitlab.isc.org/isc-projects/kea/issues/855.
|
|
For generic MySQL discussion about the problem, see https://bugs.mysql.com/bug.php?id=42041. For the specific Kea issue, see https://gitlab.isc.org/isc-projects/kea/issues/855.
|
|
|
|
|
|
|
|
|
|
|
|
|
... | @@ -101,12 +101,12 @@ join_buffer_size 256k=>512k |
... | @@ -101,12 +101,12 @@ join_buffer_size 256k=>512k |
|
## Kea 1.5.0-beta1
|
|
## Kea 1.5.0-beta1
|
|
The list of outstanding work items for the Kea 1.5 final release is here: https://gitlab.isc.org/isc-projects/kea/milestones/2
|
|
The list of outstanding work items for the Kea 1.5 final release is here: https://gitlab.isc.org/isc-projects/kea/milestones/2
|
|
Significant known issues include:
|
|
Significant known issues include:
|
|
* The congestion control mechanism, implemented to ensure Kea is processing current, rather than stale, requests when under very heavy load, can also decrease overall throughput under extremely heavy load.
|
|
* The congestion control mechanism, implemented to ensure Kea is processing current, rather than stale, requests when under very heavy load, can also decrease overall throughput under extremely heavy load.
|
|
* 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.
|
|
|
|
|
... | @@ -118,12 +118,12 @@ Significant known issues include: |
... | @@ -118,12 +118,12 @@ Significant known issues include: |
|
|
|
|
|
* The unit-tests for Forensic Logger, a premium hook library, incorrectly construct expected log file name on first through ninth day of each month. As a result, the unit-tests incorrectly signal a non-existing problem. This is only a unit-test issue and does not affect production code. For fix of this problem, see #5666.
|
|
* The unit-tests for Forensic Logger, a premium hook library, incorrectly construct expected log file name on first through ninth day of each month. As a result, the unit-tests incorrectly signal a non-existing problem. This is only a unit-test issue and does not affect production code. For fix of this problem, see #5666.
|
|
|
|
|
|
## 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.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}}}
|
|
* The DHCPv4, DHCPv6 and D2 daemons are not able to parse a Control Agent section (#5176) in their configuration file. As a simple work around, please keep the Control Agent configuration in a separate file.
|
|
* The DHCPv4, DHCPv6 and D2 daemons are not able to parse a Control Agent section (#5176) in their configuration file. As a simple work around, please keep the Control Agent configuration in a separate file.
|
... | @@ -131,7 +131,7 @@ Significant known issues include: |
... | @@ -131,7 +131,7 @@ Significant known issues include: |
|
* The following unit-tests may fail on some systems: DStubControllerTest, !NameChangeTransactionTest (6 tests), !DnsClientTest (4 tests), D2UpdateMgr (4 tests), QueueMgrUDPTest (2 tests) and D2ProcessTest (6 tests). The issues are believed to be problems with the unit-tests, not with the production code issues. Over 4000 of remaining tests will pass. If you see any of those tests fail, you may wish to rebuild using the boost-system library (specify --with-boost-libs=lboost-system when running {{{configure}}}) or without optimization (Set the CXXFLAGS environment variable to -O0 before running {{{configure}}}).
|
|
* The following unit-tests may fail on some systems: DStubControllerTest, !NameChangeTransactionTest (6 tests), !DnsClientTest (4 tests), D2UpdateMgr (4 tests), QueueMgrUDPTest (2 tests) and D2ProcessTest (6 tests). The issues are believed to be problems with the unit-tests, not with the production code issues. Over 4000 of remaining tests will pass. If you see any of those tests fail, you may wish to rebuild using the boost-system library (specify --with-boost-libs=lboost-system when running {{{configure}}}) or without optimization (Set the CXXFLAGS environment variable to -O0 before running {{{configure}}}).
|
|
* Several unit-tests may fail on systems with kernels that do not support the SO_REUSEPORT socket option. One example of such system is !RedHat Enterprise Linux 6.4 or earlier. This is considered a minor flaw in the tests and should not affect production code.
|
|
* Several unit-tests may fail on systems with kernels that do not support the SO_REUSEPORT socket option. One example of such system is !RedHat Enterprise Linux 6.4 or earlier. This is considered a minor flaw in the tests and should not affect production code.
|
|
|
|
|
|
## Kea 1.2.0-beta
|
|
## Kea 1.2.0-beta
|
|
|
|
|
|
* When Kea-shell is enabled (--enable-shell) and installation is done to default directory (no --prefix specified), kea-shell will install, but will not work. To work around the issue, please use --prefix=/usr/local if you want to install to the default directory (#5214).
|
|
* When Kea-shell is enabled (--enable-shell) and installation is done to default directory (no --prefix specified), kea-shell will install, but will not work. To work around the issue, please use --prefix=/usr/local if you want to install to the default directory (#5214).
|
|
* DHCPv4, DHCPv6 and D2 daemons are not able to parse Control Agent section (#5176). As a simple work around, please keep CA configuration in a separate file.
|
|
* DHCPv4, DHCPv6 and D2 daemons are not able to parse Control Agent section (#5176). As a simple work around, please keep CA configuration in a separate file.
|
... | @@ -139,7 +139,7 @@ Significant known issues include: |
... | @@ -139,7 +139,7 @@ Significant known issues include: |
|
* The following unit-tests may fail on some systems: !HttpListenerTest (3 tests), DStubControllerTest, !NameChangeTransactionTest (6 tests), !DnsClientTest (4 tests), D2UpdateMgr (4 tests), QueueMgrUDPTest (2 tests) and D2ProcessTest (6 tests). The issues are believed to be unit-test issues, not production code issues. Over 4000 of remaining tests will pass. If you see any of those tests fail, you may wish to rebuild either using --with-boost-libs=lboost-system or without optimization (-O0).
|
|
* The following unit-tests may fail on some systems: !HttpListenerTest (3 tests), DStubControllerTest, !NameChangeTransactionTest (6 tests), !DnsClientTest (4 tests), D2UpdateMgr (4 tests), QueueMgrUDPTest (2 tests) and D2ProcessTest (6 tests). The issues are believed to be unit-test issues, not production code issues. Over 4000 of remaining tests will pass. If you see any of those tests fail, you may wish to rebuild either using --with-boost-libs=lboost-system or without optimization (-O0).
|
|
* Several unit-tests may fail on systems with kernels that do not support SO_REUSEPORT socket option. One example of such system is RedHat Enterprise Linux 6.4 or earlier. This is consider a minor flaw in the tests and should not affect production code.
|
|
* Several unit-tests may fail on systems with kernels that do not support SO_REUSEPORT socket option. One example of such system is RedHat Enterprise Linux 6.4 or earlier. This is consider a minor flaw in the tests and should not affect production code.
|
|
|
|
|
|
## Kea 1.1.0-beta, 1.1.0 (final)
|
|
## Kea 1.1.0-beta, 1.1.0 (final)
|
|
|
|
|
|
* When Kea is compiled with unit tests and the --with-dhcp-mysql configuration option is specified, the "mysql.host_reservation-upgrade" unit test may fail on some systems. The test misinterprets output from a MySQL query. This is considered a test bug.
|
|
* When Kea is compiled with unit tests and the --with-dhcp-mysql configuration option is specified, the "mysql.host_reservation-upgrade" unit test may fail on some systems. The test misinterprets output from a MySQL query. This is considered a test bug.
|
|
|
|
|
... | @@ -156,7 +156,7 @@ Significant known issues include: |
... | @@ -156,7 +156,7 @@ 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.)
|
|
|
|
|
... | @@ -176,7 +176,7 @@ Significant known issues include: |
... | @@ -176,7 +176,7 @@ Significant known issues include: |
|
|
|
|
|
* Creating host reservations in DHCPv4 using client identifier (or DUID) is currently not supported but the configuration parsing code will accept the "duid" parameter in the reservation configuration. The server misinterprets the value specified for this parameter, so it MUST NOT be used until the client identifier based host reservations are properly implemented and documented.
|
|
* Creating host reservations in DHCPv4 using client identifier (or DUID) is currently not supported but the configuration parsing code will accept the "duid" parameter in the reservation configuration. The server misinterprets the value specified for this parameter, so it MUST NOT be used until the client identifier based host reservations are properly implemented and documented.
|
|
|
|
|
|
## Kea 0.9.2
|
|
## Kea 0.9.2
|
|
|
|
|
|
* 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.)
|
|
|
|
|
... | @@ -188,7 +188,7 @@ Significant known issues include: |
... | @@ -188,7 +188,7 @@ Significant known issues include: |
|
|
|
|
|
* Configuration option --disable-rpath is not working. Binaries always have hard coded RPATH value. See #3738 for details.
|
|
* Configuration option --disable-rpath is not working. Binaries always have hard coded RPATH value. See #3738 for details.
|
|
|
|
|
|
## Kea 0.9.2-beta
|
|
## Kea 0.9.2-beta
|
|
|
|
|
|
* Kea doesn't handle missing lease database configuration properly. See ticket #3892. When the lease database configuration is missing, Kea will try to run but the server will produce errors on each attempt to access the database. The workaround: always make sure that the lease database configuration is specified.
|
|
* Kea doesn't handle missing lease database configuration properly. See ticket #3892. When the lease database configuration is missing, Kea will try to run but the server will produce errors on each attempt to access the database. The workaround: always make sure that the lease database configuration is specified.
|
|
|
|
|
... | @@ -202,7 +202,7 @@ Significant known issues include: |
... | @@ -202,7 +202,7 @@ Significant known issues include: |
|
|
|
|
|
* When using the beta tarball, the -W feature for tools will report wrong build information. Consult your config.report file in the source tree instead. See ticket #3929 for details.
|
|
* When using the beta tarball, the -W feature for tools will report wrong build information. Consult your config.report file in the source tree instead. See ticket #3929 for details.
|
|
|
|
|
|
## Kea 0.9.1
|
|
## Kea 0.9.1
|
|
|
|
|
|
* The kea-admin script does not support upgrading the lease file from 0.9 to 0.9.1 yet. See #3601 for details.
|
|
* The kea-admin script does not support upgrading the lease file from 0.9 to 0.9.1 yet. See #3601 for details.
|
|
|
|
|
... | @@ -220,7 +220,7 @@ Significant known issues include: |
... | @@ -220,7 +220,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
|
|
|
|
|
... | @@ -238,13 +238,13 @@ Significant known issues include: |
... | @@ -238,13 +238,13 @@ Significant known issues include: |
|
|
|
|
|
* Configure option --disable-rpath is not working. Binaries always have hard coded RPATH value. See #3738 for details.
|
|
* Configure option --disable-rpath is not working. Binaries always have hard coded RPATH value. See #3738 for details.
|
|
|
|
|
|
## Kea 0.9
|
|
## Kea 0.9
|
|
|
|
|
|
* We need to audit our handling of administrative passwords. See ticket 3645 for example. Currently there are some areas where the MySQL or Kea admin password could be exposed.
|
|
* We need to audit our handling of administrative passwords. See ticket 3645 for example. Currently there are some areas where the MySQL or Kea admin password could be exposed.
|
|
|
|
|
|
* The admin scripting may not be entirely compatible across scripting systems. We have been using BASH, which has some enhancements not included in vanilla SSH
|
|
* The admin scripting may not be entirely compatible across scripting systems. We have been using BASH, which has some enhancements not included in vanilla SSH
|
|
|
|
|
|
* The default Kea configuration file kea.conf contains an invalid example of the IPv4 pool declaraion - see ticket #3538 for details.
|
|
* The default Kea configuration file kea.conf contains an invalid example of the IPv4 pool declaration - see ticket #3538 for details.
|
|
|
|
|
|
* The kea.conf file contains invalid logger configuration; it specifies the configuration for the logger called "kea" whereas it should have 3 logger entries for "kea-dhcp4", "kea-dhcp6" and "kea-dhcp-ddns"
|
|
* The kea.conf file contains invalid logger configuration; it specifies the configuration for the logger called "kea" whereas it should have 3 logger entries for "kea-dhcp4", "kea-dhcp6" and "kea-dhcp-ddns"
|
|
|
|
|
... | @@ -267,7 +267,7 @@ For DHCPv4 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp4- |
... | @@ -267,7 +267,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.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).
|
... | @@ -284,7 +284,7 @@ For DHCPv4 server limitations, see http://kea.isc.org/docs/kea-guide.html#dhcp4- |
... | @@ -284,7 +284,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:
|
... | @@ -297,4 +297,4 @@ Significant known issues with the DHCP servers in this release are: |
... | @@ -297,4 +297,4 @@ Significant known issues with the DHCP servers in this release are: |
|
|
|
|
|
* Support for operating systems other than Linux is partial. Kea lacks the capability to send DHCPv4 responses to directly connected clients. This affects all BSD systems, including Mac OS X. Kea is currently being tested on Linux only.
|
|
* Support for operating systems other than Linux is partial. Kea lacks the capability to send DHCPv4 responses to directly connected clients. This affects all BSD systems, including Mac OS X. Kea is currently being tested on Linux only.
|
|
|
|
|
|
We would appreciate feedback on usability and reports of any DHCP bugs. Please contribute your experiences to the Kea users mailing list: https://lists.isc.org/mailman/listinfo/kea-users |
|
We would appreciate feedback on usability and reports of any DHCP bugs. Please contribute your experiences to the Kea users mailing list: https://lists.isc.org/mailman/listinfo/kea-users |
|
\ No newline at end of file |
|
|