Project

General

Profile

Actions
Copy link

action #124209

closed

[qe-core] Testing of PED-2828: ISC Kea DHCP server

Added by szarate almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
dvenkatachala
Category:
New test
Target version:
QA (public) - QE-Core: Ready
Start date:
2023-05-25
Due date:
2023-05-25
% Done:

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: April Sprint 23 (Apr 05 - May 03)
Tags:
qe-core-march-sprint, qe-core-february-sprint

Description

Since ISC DCHP is now EOL since Dec 2022, there's a new DHCP server Stack, which is already in ALP, but needs to be tested.

It is a containerized solution, and the details are pretty straight forward but we need to understand how to test it and how to set up multi-machine tests for this case.

Related issues 2 (0 open — 2 closed)

Related to ALP - coordination #125846: [epic] March Prototype testingResolved2023-03-13

Actions
Related to openQA Tests (public) - action #117616: [qe-core] How to start the firewalld containerResolveddvenkatachala2023-05-252023-05-25

Actions
Actions
Copy link
 #1

Updated by szarate almost 2 years ago

  • Tags set to qe-core-february-sprint
  • Project changed from 46 to openQA Tests (public)
  • Description updated (diff)
  • Category changed from New test to New test
Actions
Copy link
 #2

Updated by szarate almost 2 years ago

  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by szarate almost 2 years ago

I think we can have this in workable as the ticket is kind of self-explanatory, Let me know if there's not enough info!

Actions
Copy link
 #4

Updated by dvenkatachala almost 2 years ago

  • Assignee set to dvenkatachala
Actions
Copy link
 #5

Updated by szarate almost 2 years ago

  • Subject changed from [qe-core] Testing of PED-2452: ISC Kea DHCP server to [qe-core] Testing of PED-2828: ISC Kea DHCP server
Actions
Copy link
 #6

Updated by szarate almost 2 years ago

  • Sprint changed from QE-Core: February Sprint (Feb 08 - Mar 08) to QE-Core: March Sprint (Mar 08 - Apr 05)
Actions
Copy link
 #7

Updated by ph03nix almost 2 years ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #8

Updated by dvenkatachala almost 2 years ago

I manually tested Kea dhcp4 server using the following steps,

  1. Modified default configuration by editing /etc/kea/kea-dhcp4.conf

  2. Started the dhcp container for dhcp4,
    podman container runlabel run registry.opensuse.org/suse/alp/workloads/tumbleweed_containerfiles/suse/alp/workloads/kea:latest for dhcp4

  3. Tested the dhcp by connecting 2 clients.
    DHCP server assigns an ip address to one client from a pool of available addresses and second client gets ip address based on its mac.

Logs from DHCP server: 

2023-03-09 15:14:55.394 INFO  [kea-dhcp4.dhcp4/1.140596574292096] DHCP4_STARTED Kea DHCPv4 server version 2.2.0 started
2023-03-09 15:14:58.947 INFO  [kea-dhcp4.leases/1.140596574292096] DHCP4_INIT_REBOOT [hwtype=1 52:54:00:10:17:41], cid=[01:52:54:00:10:17:41], tid=0xdc2bdda3: client is in INIT-REBOOT state and requests address 192.0.2.101
2023-03-09 15:14:58.983 INFO  [kea-dhcp4.leases/1.140596574292096] DHCP4_INIT_REBOOT [hwtype=1 52:54:00:12:ce:be], cid=[01:52:54:00:12:ce:be], tid=0x7734509e: client is in INIT-REBOOT state and requests address 192.0.2.102
2023-03-09 15:15:00.947 INFO  [kea-dhcp4.leases/1.140596574292096] DHCP4_LEASE_ADVERT [hwtype=1 52:54:00:10:17:41], cid=[01:52:54:00:10:17:41], tid=0xd4b987cd: lease 192.0.2.201 will be advertised
2023-03-09 15:15:00.948 INFO  [kea-dhcp4.leases/1.140596574292096] DHCP4_LEASE_ALLOC [hwtype=1 52:54:00:10:17:41], cid=[01:52:54:00:10:17:41], tid=0xd4b987cd: lease 192.0.2.201 has been allocated for 3600 seconds
2023-03-09 15:15:00.992 INFO  [kea-dhcp4.leases/1.140596574292096] DHCP4_LEASE_ADVERT [hwtype=1 52:54:00:12:ce:be], cid=[01:52:54:00:12:ce:be], tid=0xcd3b42e0: lease 192.0.2.102 will be advertised
Actions
Copy link
 #9

Updated by szarate almost 2 years ago

Actions
Copy link
 #10

Updated by szarate almost 2 years ago

  • Related to action #117616: [qe-core] How to start the firewalld container added
Actions
Copy link
 #11

Updated by dvenkatachala almost 2 years ago

PR created: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16736.

The next step is to start automating DHCP6 tests in multi-machine. Also, I manually tested the Kea DHCPv6 server, and it is working as expected.

Actions
Copy link
 #12

Updated by szarate over 1 year ago

  • Sprint changed from QE-Core: March Sprint (Mar 08 - Apr 05) to QE-Core: April Sprint 23 (Apr 05 - May 03)
Actions
Copy link
 #14

Updated by dvenkatachala over 1 year ago

Tests Kea DHCP4 and DHCP6 worker containers scheduled in the alp-micro job group,they are working fine.
https://openqa.opensuse.org/tests/overview?distri=alp&version=micro-0.1&build=3.5&groupid=108

Actions
Copy link
 #15

Updated by dvenkatachala over 1 year ago

  • Status changed from In Progress to Resolved

Currently,tests are scheduled in ALP Micro job group.
After the discussion with team-members, workload container will be tested in ALP Bedrock and I will move this tests from ALP Micro to ALP Bedrock job group.

Actions
Copy link

Also available in: Atom PDF