Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2019-03-20T09:04:02Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/481remote-subnet4-set inconsistent work when id/subnet is duplicated.2019-03-20T09:04:02ZWlodzimierz Wencelremote-subnet4-set inconsistent work when id/subnet is duplicated.1. Kea is started without any subnet configured.
1. execute command `remote-subnet4-set`:
```
{"command": "remote-subnet4-set",
"arguments": {"subnets": [{"interface": "enp0s9",
"subnet": "192.168...1. Kea is started without any subnet configured.
1. execute command `remote-subnet4-set`:
```
{"command": "remote-subnet4-set",
"arguments": {"subnets": [{"interface": "enp0s9",
"subnet": "192.168.50.0/24",
"pools": [{"pool": "192.168.50.1-192.168.50.100"}],
"id": 5}],
"server-tags": ["abc"],
"remote": {"type": "mysql"}
}
}
```
3. Kea will be configured correctly with subnet 192.168.50.0/24 with id 5.
4. Let's now execute command `remote-subnet4-set` with different subnet but with the same value of id:
```
{"command": "remote-subnet4-set",
"arguments": {"subnets": [{"interface": "enp0s9",
"subnet": "192.168.51.0/24",
"pools": [{"pool": "192.168.51.1-192.168.51.100"}],
"id": 5}],
"server-tags": ["abc"],
"remote": {"type": "mysql"}
}
}
```
```
{
"arguments": {
"subnets": [
{
"id": 5,
"subnet": "192.168.51.0/24"
}
]
},
"result": 0,
"text": "IPv4 subnet successfully set."
}
```
```
mysql> select * from dhcp4_subnet;
+-----------+-----------------+---------------+------------------+------------+----------------+--------------+-----------+-----------------+---------------------+-------------+--------------+-------+-------------+------------------------+------------------+-----------------+---------------------+--------------+----------------+
| subnet_id | subnet_prefix | 4o6_interface | 4o6_interface_id | 4o6_subnet | boot_file_name | client_class | interface | match_client_id | modification_ts | next_server | rebind_timer | relay | renew_timer | require_client_classes | reservation_mode | server_hostname | shared_network_name | user_context | valid_lifetime |
+-----------+-----------------+---------------+------------------+------------+----------------+--------------+-----------+-----------------+---------------------+-------------+--------------+-------+-------------+------------------------+------------------+-----------------+---------------------+--------------+----------------+
| 5 | 192.168.51.0/24 | NULL | NULL | NULL | NULL | NULL | enp0s9 | 1 | 2019-02-19 06:05:39 | NULL | NULL | NULL | NULL | [ ] | 3 | NULL | NULL | NULL | 7200 |
+-----------+-----------------+---------------+------------------+------------+----------------+--------------+-----------+-----------------+---------------------+-------------+--------------+-------+-------------+------------------------+------------------+-----------------+---------------------+--------------+----------------+
```
result: there is now just one subnet configured and it's `192.168.51.0/24` so previous one was overwritten without warning/notification
5. But when second command will duplicated subnet kea will respond with a bit cryptic error:
```
{
"result": 1,
"text": "unable to execute for <INSERT INTO dhcp4_pool( start_address, end_address, subnet_id, modification_ts) VALUES (?, ?, ?, ?)>, reason: Cannot add or update a child row: a foreign key constraint fails (`keadb`.`dhcp4_pool`, CONSTRAINT `fk_dhcp4_pool_subnet_id` FOREIGN KEY (`subnet_id`) REFERENCES `dhcp4_subnet` (`subnet_id`) ON DELETE CASCADE ON UPDATE CASCADE) (error code 1452)"
}
```
`id` and `subnet` are two ways of exactly identify record in database so I guess it should work in the same manner. Either override, or return error saying that there is such record in the database.Kea1.6https://gitlab.isc.org/isc-projects/kea/-/issues/480Fix shellcheck issues in Kea scripts2019-03-15T23:23:29ZTomek MrugalskiFix shellcheck issues in Kea scripts@ondrej pointed out that shellcheck, a tool that sanitizes shell scripts, reported issues in keactrl.
This task is about addressing those issues in keactrl and checking other user-visible scripts.
The tool is available as on-line servi...@ondrej pointed out that shellcheck, a tool that sanitizes shell scripts, reported issues in keactrl.
This task is about addressing those issues in keactrl and checking other user-visible scripts.
The tool is available as on-line service (https://www.shellcheck.net/), but also as command line tool.
Moved this directly to 1.6, because it's coming from Debian package maintainer, so it's related to an objective of 1.6.Kea1.6Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/478Improve error message: "Database access parameter 'type' does not specify a s...2019-03-06T20:25:35ZCathy AlmondImprove error message: "Database access parameter 'type' does not specify a supported database backend:mysql"---
name: Improve error message: "Database access parameter 'type' does not specify a supported database backend:mysql"
about: Please make it clearer why this error is being emitted. The 'type' is a valid configuration option. The prob...---
name: Improve error message: "Database access parameter 'type' does not specify a supported database backend:mysql"
about: Please make it clearer why this error is being emitted. The 'type' is a valid configuration option. The problem is that the build does not include support for mysql back-end.
---
These error messages don't explain well what the problem is and where to look to fix it:
> root@debian:/opt/kea-1.5.0# 2019-02-18 17:26:12.746 ERROR [kea-dhcp4.dhcp4/51240] DHCP4_CONFIG_LOAD_FAIL configuration error using file: /usr/local/etc/kea/kea-dhcp4.conf, reason: Unable to open database: Database access parameter 'type' does not specify a supported database backend:mysql
> 2019-02-18 17:26:12.746 ERROR [kea-dhcp4.dhcp4/51240] DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file '/usr/local/etc/kea/kea-dhcp4.conf': Unable to open database: Database access parameter 'type' does not specify a supported database backend:mysql
A better message would be something like:
"Unable to open database: The Kea server has not been built with support for database type: mysql"
See [#14213](https://support.isc.org/Ticket/Display.html?id=14213)Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/474RADIUS with shared networks2019-05-15T12:50:03ZTomek MrugalskiRADIUS with shared networksWhen RADIUS was implemented, we didn't have shared networks support. As a result, there was a mechanism designed (subnet-reselect) to do something a bit similar to shared networks.
We need to look at the code and see:
- what is needed t...When RADIUS was implemented, we didn't have shared networks support. As a result, there was a mechanism designed (subnet-reselect) to do something a bit similar to shared networks.
We need to look at the code and see:
- what is needed to make RADIUS work with shared network
- what the limitations would be
RADIUS has some substantial limitations as a database-like system, but the basic assumption that it can return attributes that are mapped to client classes should be viable.
#403 has a discussion about current (1.5) code and its limitations.Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/471Hammer build tool should be internal2019-03-06T14:28:15ZTomek MrugalskiHammer build tool should be internalWe discussed this on 2019-02-07 call and the overall consensus was make it internal. It's not really hidden, just we don't want to distribute it in a tarball.
1. Need to tweak makefiles.
1. Need to remove the user's guide section (but t...We discussed this on 2019-02-07 call and the overall consensus was make it internal. It's not really hidden, just we don't want to distribute it in a tarball.
1. Need to tweak makefiles.
1. Need to remove the user's guide section (but the content was useful, perhaps turn this into a text printed out when calling ./hammer.py --tutorial or something similar)Kea1.6https://gitlab.isc.org/isc-projects/kea/-/issues/4681.5.0 sanity checks follow-up: clean README/INSTALL in premium2019-02-19T09:15:08ZTomek Mrugalski1.5.0 sanity checks follow-up: clean README/INSTALL in premium#344 was a nice place to report issues discovered in 1.5.0 sanity checks. Most of them are addressed or have their own issues now, except the problem of README and INSTALL files in premium repository. The [original problem description](h...#344 was a nice place to report issues discovered in 1.5.0 sanity checks. Most of them are addressed or have their own issues now, except the problem of README and INSTALL files in premium repository. The [original problem description](https://gitlab.isc.org/isc-projects/kea/issues/344#note_35992) was:
INSTALL and README files could be improved in hook tarballs:
* README mentions section 14.4 (should be 15.4) or better yet say "15.4 "Available hook libraries". This way people could find it if get the numbering wrong again.
* README mentions section 14.2 (should be 15.2 "Installing hook packages")
* INSTALL mentions 14.2 (should be 15.2)
* INSTALL mentions kea-<packagename>-beta.tar.gz (the "-beta" part should be removed).Kea1.6Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/465Add subnet4-update and subnet6-update commands to subnet-cmds hook [ISC-suppo...2019-04-19T11:25:18ZVicky Riskvicky@isc.orgAdd subnet4-update and subnet6-update commands to subnet-cmds hook [ISC-support #14130]In order to update an existing subnet, you (currently) have to first delete it and then add it.
When making a small change to a large number of subnets, this can create excessive amount of traffic.
Could we please have additional comman...In order to update an existing subnet, you (currently) have to first delete it and then add it.
When making a small change to a large number of subnets, this can create excessive amount of traffic.
Could we please have additional commands to update an existing subnet?
This was part of the original design, but we didn't implement it at the time (likely ran out of time)
https://gitlab.isc.org/isc-projects/kea/wikis/designs/commands#24-subnets-management
S.7. Kea MAY support the #FF0000 subnet4-update command.
S.8. Kea MAY support the #FF0000 subnet6-update command.
From the wiki:
Those two commands allow making changes to an existing subnet: changing prefix, prefix length, T1, T2, preferred lifetime, valid lifetime timers, allowed client classes, subnet specific options, and subnet-id values. It also allows modifying pools.
Kea1.6Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/464Kea DHCPv4 not able to send vendor options if client doesn't send vivso2019-02-19T12:04:48ZTomek MrugalskiKea DHCPv4 not able to send vendor options if client doesn't send vivsoA customer reported a problem that Kea is unable to send back vivso sub-options. Kea sends only the top-level vivso option with correct vendor-id, but is not able to send back any sub-options.
The problem has been investigated and this ...A customer reported a problem that Kea is unable to send back vivso sub-options. Kea sends only the top-level vivso option with correct vendor-id, but is not able to send back any sub-options.
The problem has been investigated and this is caused by the Genexis clients that do not send vivso option itself. That way, the server is not able to figure out what vendor-id to use.
In ideal world, Genexis client would send vivso with enterprise value set to 25167. But they don't and we need to tweak Kea to be able to work around that.Kea1.6Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/463Ordering using timestamps without fractional part fails on MySQL 82019-02-19T09:42:17ZFrancis DupontOrdering using timestamps without fractional part fails on MySQL 8Found on my Fedora 29 with community MySQL 8: some get-all unit tests of the MySQL VB hook failed to retrieve audit records in the expected order and all records have the same timestamp.
Fortunately the fix is easy: sort same timestamp ...Found on my Fedora 29 with community MySQL 8: some get-all unit tests of the MySQL VB hook failed to retrieve audit records in the expected order and all records have the same timestamp.
Fortunately the fix is easy: sort same timestamp records using the auto-increment id.
Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/460Update MySQL database schema for DHCPv6 config backend.2019-02-22T22:59:28ZFrancis DupontUpdate MySQL database schema for DHCPv6 config backend.This includes 2 MRs: one to align DHCPv4 and DHCPv6 definitions, the second to add missing DHCPv6 stuff, i.e. things added fro DHCPv4 but not yet for DHCPv6.This includes 2 MRs: one to align DHCPv4 and DHCPv6 definitions, the second to add missing DHCPv6 stuff, i.e. things added fro DHCPv4 but not yet for DHCPv6.Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/458Config backend support in src/lib2019-02-20T10:03:37ZFrancis DupontConfig backend support in src/libIncludes all the src/lib code at one exception to support DHCPv6 in config backends.Includes all the src/lib code at one exception to support DHCPv6 in config backends.Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/454avalanche mode for perfdhcp: measure how long it takes to provision X clients2019-10-17T14:34:17ZTomek Mrugalskiavalanche mode for perfdhcp: measure how long it takes to provision X clientsA customer is reporting a depressingly low performance with proxy MySQL. The numbers they get are radically different compared to what we get in perflab.
The usage scenario is a CMTS rebooting 4000 cable modems (clients) behind it askin...A customer is reporting a depressingly low performance with proxy MySQL. The numbers they get are radically different compared to what we get in perflab.
The usage scenario is a CMTS rebooting 4000 cable modems (clients) behind it asking for leases. The goal of this mode is to measure how long it takes to provision specified number of clients. An important factor here is that the clients that don't get a response within a second start a retransmission (search for exponential backoff in [RFC2131](https://tools.ietf.org/html/rfc2131)).
I can imagine something like this:
```
./perfdhcp --provision-clients 4000
...
...
It took 123.456s to provision 4000 clients. 5678 packets were sent, 1234 retransmissions needed, received 8000 responses.
```
This is only a proposal. The feature may look and work differently. The goal is to have something better than we have now to simulate actual real life scenario of mass client reboot.Kea1.6Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/kea/-/issues/451MySQL config backend must not set timers to default value of 02019-02-08T13:26:38ZMarcin SiodelskiMySQL config backend must not set timers to default value of 0Currently, when the MySQL Config Backend finds NULL DHCP timer value (e.g. renew-timer) it will use a value of 0 as a default. The subnet logic, though, treats unspecified value differently than the 0 value. The 0 value has a meaning (at...Currently, when the MySQL Config Backend finds NULL DHCP timer value (e.g. renew-timer) it will use a value of 0 as a default. The subnet logic, though, treats unspecified value differently than the 0 value. The 0 value has a meaning (at least in v6) that it is up to the client to determine when to renew. The unspecified value causes the server to calculate the times based on the percentages.
We need to adjust the backend to store unspecified timers (triplets) as NULL. Then, the backend has to turn NULLs to unspecified triplets.Kea1.6Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/448Update remote-global-parmeter4-set (cb_cmds) to handle other parameter types ...2019-02-21T12:13:50ZMarcin SiodelskiUpdate remote-global-parmeter4-set (cb_cmds) to handle other parameter types than stringsWe have recently extended the `dhcp4_global_parameter` table to include the native type of the global parameter. This was required because the global parameters are held in the database as strings. The server needs to know the types of t...We have recently extended the `dhcp4_global_parameter` table to include the native type of the global parameter. This was required because the global parameters are held in the database as strings. The server needs to know the types of the parameters to correctly interpret them. Today, the `remote-global-parameter4-set` command can only store a string in the database. We need to extend it to also accept other types. The following section in the design:
https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-global-parameter4-set
describes the variants of the command to be supported.Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/444mysql/upgrade_7.0_to_8.0.sh script failure on debian82019-02-08T12:55:02ZWlodzimierz Wencelmysql/upgrade_7.0_to_8.0.sh script failure on debian8Error:
```
test@debian8-64-1-dhcp:~/jenkins_lab/var/area_A/sbin$ ./kea-admin lease-upgrade mysql -u kea -p kea -n kea
Lease DB version reported before upgrade: 7.0
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/up...Error:
```
test@debian8-64-1-dhcp:~/jenkins_lab/var/area_A/sbin$ ./kea-admin lease-upgrade mysql -u kea -p kea -n kea
Lease DB version reported before upgrade: 7.0
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_1.0_to_2.0.sh file...
This script upgrades 1.0 to 2.0. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_2.0_to_3.0.sh file...
This script upgrades 2.0 to 3.0. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_3.0_to_4.0.sh file...
This script upgrades 3.0 to 4.0. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_4.0_to_4.1.sh file...
This script upgrades 4.0 to 4.1. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_4.1_to_5.0.sh file...
This script upgrades 4.1 to 5.0. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_5.0_to_5.1.sh file...
This script upgrades 5.0 to 5.1. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_5.1_to_5.2.sh file...
This script upgrades 5.1 to 5.2. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_5.2_to_6.0.sh file...
This script upgrades 5.2 to 6.0. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_6.0_to_7.0.sh file...
This script upgrades 6.0 to 7.0. Reported version is 7.0. Skipping upgrade.
Processing /home/test/jenkins_lab/var/area_A/share/kea/scripts/mysql/upgrade_7.0_to_8.0.sh file...
ERROR 1064 (42000) at line 8: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL' at line 2
Lease DB version reported after upgrade: 7.0
```
Versions installed
```
test@debian8-64-1-dhcp:~/jenkins_lab/var/area_A/sbin$ ./kea-dhcp6 -V
1.5.0-git
git f72bb0f7a221a422a7f03cfd04e0c21df8d33b0e
linked with:
log4cplus 1.0.4
Botan 1.10.8 (released 20140410, revision mtn:3e5da04321de05a3ae1f7177e0dd2191e598dca7, distribution unspecified)
database:
MySQL backend 8.0, library 5.5.62
PostgreSQL backend 5.0, library 90420
Memfile backend 2.1
```
```
MySQL:
MYSQL_VERSION: 5.5.62
MYSQL_CPPFLAGS: -I/usr/include/mysql -DBIG_JOINS=1 -fno-strict-aliasing -g -DNDEBUG
MYSQL_LIBS: -L/usr/lib/x86_64-linux-gnu -lmysqlclient -lpthread -lz -lm -ldl
```
OS:
```
test@debian8-64-1-dhcp:~/jenkins_lab/var/area_A/sbin$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
```Kea1.6Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/441make distcheck fails on fedora 29 (automake 1.16)2019-03-13T13:28:52ZMichal Nowikowskimake distcheck fails on fedora 29 (automake 1.16)Failure can be found on Jenkins:
https://jenkins.isc.org/job/kea-master-distcheck/194/execution/node/99/log/
Hypothesis is that it fails due to wrong dependency generated by automake or some missing dependencies on Kea side.
In src/lib/...Failure can be found on Jenkins:
https://jenkins.isc.org/job/kea-master-distcheck/194/execution/node/99/log/
Hypothesis is that it fails due to wrong dependency generated by automake or some missing dependencies on Kea side.
In src/lib/log/tests/Makefile generated on Fedora 29 there is distdir that depends on BUILT_SOURCES which depend
on log_test_messages.{c|hh} which depend on s-messages which uses src/lib/log/compiler/kea-msg-compiler. As can be seen in this chain there is no dependency on this compiler. On other systems distdir does not depend on BUILT_SOURCES and due to this it works there.
My proposed solution is getting rid of this semi-circular dependency for compiling some source to generate some other source for further compilation and replace this compiler with compiler written in some interpreted language (e.g. Python) that does not require compilation.Kea1.6Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/440Extend CB API: return all subnets belonging to a given shared network2019-02-05T10:18:24ZMarcin SiodelskiExtend CB API: return all subnets belonging to a given shared networkIt came up during implementation of the `remote-network4-get` command. When querying for a shared network, only the shared network specific parameters are returned. It doesn't include any information about the subnets belonging to a shar...It came up during implementation of the `remote-network4-get` command. When querying for a shared network, only the shared network specific parameters are returned. It doesn't include any information about the subnets belonging to a shared network. Therefore, in order to return a shared network along with the subnets we need an additional query to fetch subnets for a given shared network name.Kea1.6Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/436Update contributors guide2019-05-27T16:50:19ZTomek MrugalskiUpdate contributors guideAfter Gitlab migration our contributors guide is outdated. Need to clean it up and probably turn into a separate doc.After Gitlab migration our contributors guide is outdated. Need to clean it up and probably turn into a separate doc.Kea1.6Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/429Include global parameter data type in CB MySQL Config Backend2019-02-04T12:36:59ZMarcin SiodelskiInclude global parameter data type in CB MySQL Config BackendThe global parameters in CB are stored as strings in the database. That simplifies the structure of the database allowing for having single SQL table for all types of global parameters. However, there is an issue on the server side that ...The global parameters in CB are stored as strings in the database. That simplifies the structure of the database allowing for having single SQL table for all types of global parameters. However, there is an issue on the server side that it cannot recognize the type it should cast the parameter to when it is fetched from the database. We have decided to add a column into the `dhcpX_global_parameter` table that defines a data type. e.g. string, timestamp, real, number etc.Kea1.6Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/426cassandra unit tests ends with success even though they fail2019-02-07T14:25:22ZWlodzimierz Wencelcassandra unit tests ends with success even though they failsome of the unit tests were reported as passed even though they fail due to broken cassandra environment
```
[ RUN ] CqlLeaseMgrTest.maxDate4
/home/jenkins/workspace/kea-master-db-backends/src/share/database/scripts/cql/dhcpdb_drop...some of the unit tests were reported as passed even though they fail due to broken cassandra environment
```
[ RUN ] CqlLeaseMgrTest.maxDate4
/home/jenkins/workspace/kea-master-db-backends/src/share/database/scripts/cql/dhcpdb_drop.cql:19:OperationTimedOut: errors={'127.0.0.1': 'Client request timeout. See Session.execute[_async](timeout)'}, last_host=127.0.0.1
/home/jenkins/workspace/kea-master-db-backends/src/share/database/scripts/cql/dhcpdb_drop.cql:20:OperationTimedOut: errors={'127.0.0.1': 'Client request timeout. See Session.execute[_async](timeout)'}, last_host=127.0.0.1
runCqlSchema failed:cqlsh -u keatest -p keatest -k keatest -f/home/jenkins/workspace/kea-master-db-backends/src/share/database/scripts/cql/dhcpdb_drop.cql
[ OK ] CqlLeaseMgrTest.maxDate4 (56934 ms)
```
there are more of such tests here: https://jenkins.isc.org/job/kea-master-db-backends/29/consoleText
just find `runCqlSchema failed`Kea1.6Francis DupontFrancis Dupont