-
Notifications
You must be signed in to change notification settings - Fork 837
Ignore settling with down state since it would never settle #1207
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
Conversation
mlguerrero12
left a comment
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.
ptp tests are failing due to this, could you please check @bn222?
0670505 to
66d52cc
Compare
mlguerrero12
left a comment
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.
Discussed internally with @bn222, immediately skipping SettleAddresses if the link state is not up caused adding route failures on the ptp plugin. This usually happens when the address is not present. So, it seems that the link eventually comes up and the address settles. The code relies on the delay added by this function.
For the moment, we decided to add the link status check when the deadline expires (tentative after 5s). When there is no carrier, pod creation will be delayed but it was the previous behavior anyway (returned error was always ignored). This needs to be investigated/fixed in another pr.
Signed-off-by: Balazs Nemeth <[email protected]>
|
@squeed ptal |
Ignore settling with down state since the interface would never settle. Literally that: if there is no cable, then this will error out. In the past, it didn't.