BSpendlove / pykeadhcp

A python module used to interact the the Kea DHCP API daemons (dhcp4, dhcp6, ctrl-agent and ddns)
Apache License 2.0
19 stars 4 forks source link

Premium hooks always required for running the test environment #51

Open mxsrv opened 1 year ago

mxsrv commented 1 year ago

Python version

3.10

How to reproduce this locally

  1. Build test infrastructure container without Kea Premium flag with docker compose

What should happen?

The test setup should run without requiring Kea Premium hooks.

What happened?

While trying to test a modification of pykeadhcp and thus building the test setup, we experienced the following error messages that indicate that Kea is trying to load Premium hooks, although KEA_PREMIUM was not set.

test_infrastructure-kea-1  | 2023-09-27 14:01:23.649 ERROR [kea-dhcp6.hooks/17.140330090043840] HOOKS_OPEN_ERROR failed to open hook library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_subnet_cmds.so: /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_subnet_cmds.so: cannot open shared object file: No such file or directory

test_infrastructure-kea-1  | 2023-09-27 14:01:23.649 ERROR [kea-dhcp6.hooks/17.140330090043840] HOOKS_OPEN_ERROR failed to open hook library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_class_cmds.so: /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_class_cmds.so: cannot open shared object file: No such file or directory

test_infrastructure-kea-1  | 2023-09-27 14:01:23.649 ERROR [kea-dhcp6.hooks/17.140330090043840] HOOKS_OPEN_ERROR failed to open hook library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_host_cache.so: /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_host_cache.so: cannot open shared object file: No such file or directory

I would expect that I am able to test stuff whithout requiring to have premium access.

BSpendlove commented 1 year ago

Hey @mxsrv apologies about that, it appears I've left some of the premium hooks in the base config files I use, I will build a separate config for testing premium hooks when the premium flag is used.

You should be ok to just remove all the hooks in the .conf files that are preventing you from running the containers, I will push this in the next update