Skip to content

Conversation

@bn222
Copy link
Contributor

@bn222 bn222 commented Oct 1, 2025

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.

Copy link
Member

@mlguerrero12 mlguerrero12 left a 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?

@bn222 bn222 force-pushed the main branch 4 times, most recently from 0670505 to 66d52cc Compare October 1, 2025 12:19
Copy link
Member

@mlguerrero12 mlguerrero12 left a 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.

@bn222
Copy link
Contributor Author

bn222 commented Oct 1, 2025

@squeed ptal

@mlguerrero12 mlguerrero12 merged commit 372953d into containernetworking:main Oct 2, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants