vultr: remove check_route check#2151
Conversation
987b7f8 to
6df2a19
Compare
|
I might have encountered this issue because the routes set by #2125 are different than dhclient. |
|
Is there anything I can do to help this PR move forward? |
|
Thanks for the PR @zimbatm . @eb3095 Would you mind reviewing this? |
|
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.) |
TheRealFalcon
left a comment
There was a problem hiding this comment.
I think this one has waited long enough. The changes here look good. Worst case scenario looks like we'll get a couple extra DHCP error log messages.
There's still a linting error to fix and the cla signers file will need to be rebased, but then we should be good to go on this one!
The heuristic is assuming that the URL will contain an IP, and that the route explicitly lists that IP (eg: 0.0.0.0/0 should match but doesn't). In order for the heuristic to be 100% reliable, it would have to replicate exactly what the system is doing both in terms of DNS and route resolution. Because the HTTP request below is already exercising the python nd system resolution, it is simpler to just remove this check and lean on the HTTP request to provide the answer if the network is up or not.
a2f4447 to
3c62b73
Compare
|
thanks, fixed! |
Keep support for udhcpc (waiting for upstream PR: canonical/cloud-init#4190). Vultr patch has been merged upstream (canonical/cloud-init#2151).
Proposed Commit Message
Additional Context
Test Steps
Checklist: