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

Test to install and verify kea dhcp4 server container #16736

Merged
merged 1 commit into from Apr 3, 2023

Conversation

DeepthiYV
Copy link
Contributor

@DeepthiYV DeepthiYV commented Mar 29, 2023

Add a multi-machine test to install and verify the ISC Kea DHCP4 server.

Latest VRs:
setup_dhcp4_server | DHCP4_client

@DeepthiYV DeepthiYV changed the title Add test to install and verify kea dhcp4 server container Test to install and verify kea dhcp4 server container Mar 29, 2023
@dzedro
Copy link
Contributor

dzedro commented Mar 29, 2023

Why not run in serial_terminal ?

Comment on lines 329 to 51
// else.
{
"hw-address": "1a:1b:1c:1d:1e:1f",
"ip-address": "10.0.2.201"
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this part is tested [along with the ones after]
MAC/DUID/CLIENTID etc
Can we mask them if possible? but it is not a bit deal.

use lockapi;
use mmapi;
use mm_network 'setup_static_mm_network';
use repo_tools 'add_qa_head_repo';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this line be removed?

Copy link
Contributor

@grisu48 grisu48 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job Dee! I've added some comments, but a 👍 on the general approach!

@@ -0,0 +1,461 @@
// This is a basic configuration for the Kea DHCPv4 server. Subnet declarations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No hard requirement, but I would crop the config file down to the required settings and refer to https://kea.readthedocs.io for more details. That gives us a better overview about the USED settings in the test run, as opposed to show all POSSIBLE settings.

But I guess that's more of a style question, so I leave it to you to decide if you like that or not.

@@ -29,7 +29,7 @@ sub run {
shift->wait_boot(bootloader_time => 300);
}
microos_login;
record_kernel_audit_messages(log_upload => 1);
record_kernel_audit_messages(log_upload => 1) unless (get_var('NICTYPE') eq 'tap');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we skipping this step? Is it failing?
If so, please add a comment so that our future selves will remember 🙂

my ($self) = @_;
mutex_wait 'barrier_setup_done';

assert_script_run("ip a");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this necessary or does this provide debugging information? If the later, consider using record_info instead, e.g.

record_info("ip a", script_output("ip a"));

@dzedro
Copy link
Contributor

dzedro commented Mar 31, 2023

Please update VRs

Copy link
Contributor

@rfan1 rfan1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, great work!

@DeepthiYV
Copy link
Contributor Author

Please update VRs

Updated latest VRs above.

@foursixnine foursixnine merged commit e9921f3 into os-autoinst:master Apr 3, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants