-
Notifications
You must be signed in to change notification settings - Fork 911
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
sources/azure: prevent tight loops for DHCP retries #1285
Conversation
c4fafc0
to
8f3460b
Compare
8f3460b
to
09e3b6d
Compare
09e3b6d
to
19d24ca
Compare
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.
Overall looks good, but one inline comment/question and please rebase the previous merged PR into this one.
b658333
to
4b12f46
Compare
Also updated the loop so we don't sleep if we're past the timeout. |
With debug logging, tight loops may result in huge log file sizes, e.g.: "Unable to find fallback nic" 1. Raise NoDHCPLeaseMissingDhclientError to caller if no dhclient found instead of retrying DHCP, retrying will not fix a missing dhclient. 2. For other DHCP failures, retry after sleeping one second. Signed-off-by: Chris Patterson <cpatterson@microsoft.com>
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!
With debug logging, tight loops may result in huge log file sizes, e.g.:
"Unable to find fallback nic"
Raise NoDHCPLeaseMissingDhclientError to caller if no dhclient found
instead of retrying DHCP, retrying will not fix a missing dhclient.
For other DHCP failures, retry after sleeping one second.
Signed-off-by: Chris Patterson cpatterson@microsoft.com
Depends on #1276
Would be a good candidate for SRU, if possible.