-
Notifications
You must be signed in to change notification settings - Fork 882
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(hotplug): fix race getting ipv6 #5271
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aciba90 Nice, thanks for fixing this!
A couple of minor questions, but this looks good to me!
-
I don't remember why we call the
.launch()
context manager twice, is that intentional? -
We already have
_wait_till_hotplug_complete()
, and the purpose of this operation is to wait for hotplug to complete (the outcome of hotplug, if not necessarily the systemd service). Would the fix make more sense in that function maybe?
Thanks for the reviews!
We need a second instance in the same subnet to test that connectivity works properly from there. It is explained in the test docstring.
I do not think so, as if so,
Thoughts? |
Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close. If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging TheRealFalcon, and he will ensure that someone takes a look soon. (If the pull request is closed and you would like to continue working on it, please do tag TheRealFalcon to reopen it.) |
Add retry logic for _get_ip_addr to properly get the ipv6 address. The output of `ip --brief addr` can show ens6 UP 192.168.13.34/20 metric 200 fe80::8fd:afff:fea3:f4ad/64 instead of ens6 UP 192.168.13.34/20 metric 200 2a05:d012:ea0:c500:1373:45f4:aa83:517c/128 fe80::8fd:afff:fea3:f4ad/64 if executed so early that the kernel didn't expose the wanted ipv6 address.
6e43799
to
8dd19fd
Compare
Add retry logic for _get_ip_addr to properly get the ipv6 address. The output of `ip --brief addr` can show ens6 UP 192.168.13.34/20 metric 200 fe80::8fd:afff:fea3:f4ad/64 instead of ens6 UP 192.168.13.34/20 metric 200 2a05:d012:ea0:c500:1373:45f4:aa83:517c/128 fe80::8fd:afff:fea3:f4ad/64 if executed so early that the kernel didn't expose the wanted ipv6 address.
Proposed Commit Message
Additional Context
https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-jammy-ec2/lastCompletedBuild/testReport/tests.integration_tests.modules/test_hotplug/test_multi_nic_hotplug_vpc/
Test Steps
Checklist
Merge type