Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update VRouter to Alpine 3.19 + Move kea DHCP4 hook to one-apps #93

Open
sk4zuzu opened this issue May 8, 2024 · 1 comment · May be fixed by #139
Open

Update VRouter to Alpine 3.19 + Move kea DHCP4 hook to one-apps #93

sk4zuzu opened this issue May 8, 2024 · 1 comment · May be fixed by #139
Assignees
Labels
category: virtual router Virtual Router appliance status: accepted The issue is valid and will be planned for fix or implementation type: feature A new feature planned for implementation

Comments

@sk4zuzu
Copy link
Contributor

sk4zuzu commented May 8, 2024

Using current binary kea hook in Alpine 3.19 results in:

kea-dhcp4: ERROR [kea-dhcp4.hooks.139662906213968] HOOKS_INCORRECT_VERSION hook library /usr/lib/kea/hooks/libkea-onelease-dhcp4.so is at version 20200, require version 20401

We'd like to:

  1. Move code from https://github.com/OpenNebula/addon-kea-hook-onelease4 to one-apps.
  2. Add docker/podman based kea hook build to the Makefile.
  3. Update VRouter to use Alpine 3.19 and the new kea hook binary.
@sk4zuzu sk4zuzu added type: feature A new feature planned for implementation category: virtual router Virtual Router appliance labels May 8, 2024
@aleixrm
Copy link
Member

aleixrm commented Nov 18, 2024

@aleixrm aleixrm linked a pull request Dec 2, 2024 that will close this issue
@rsmontero rsmontero added the status: accepted The issue is valid and will be planned for fix or implementation label Dec 3, 2024
@rsmontero rsmontero added this to the Release 6.10.2 milestone Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: virtual router Virtual Router appliance status: accepted The issue is valid and will be planned for fix or implementation type: feature A new feature planned for implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants