-
Notifications
You must be signed in to change notification settings - Fork 81
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
Fix Default Route check when not using DHCP #876
base: master
Are you sure you want to change the base?
Conversation
The code looks good to me. Can give different commit title for 2 commits or simply squash 2 commits into a single one? Thanks |
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.
Thanks for sending us the patch. However, I wonder if this will fix the problem. Please describe the steps to reproduce the case. A new GH issue for it would be nice (it helps us better understand the scope of the issue regarding the context and additional details provided). I want to reproduce the problem and validate if the fix suggested by this PR works.
Many thanks.
This pull request is now in conflict. Could you fix it @tayterz2? 🙏 |
840cc96
to
0f2aa50
Compare
Done - merged into a single commit. Temporarily broke everything, but fixed now! Thanks! |
Resolves harvester/harvester#7280 |
Problem:
#725 introduces a bug wherein if an automated deployment using userdata.yaml is initiated and does not use DHCP, the installation fails with the error "No default route found. Please check the router setting on the DHCP server" regardless of the "Gateway" settings. This is because the check is performed before a static network is set up.
Solution:
Add a couple of "if" checks to determine if this is a DHCP installation. If not, skip the default route check.
Related Issue:
#725 #734
Test plan:
Using this userdata.yaml file on a second ISO or PXE, successfully perform an automated install: