-
Notifications
You must be signed in to change notification settings - Fork 375
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
[Windows] Support OF port state "down" when installing Pod forwarding rules #6889
Conversation
/test-all |
/test-windows-all |
/test-all |
/test-all |
… rules On Windows, OVS has an issue which doesn't correctly update the port status after an OpenFlow port is successfully installed. So OVS may send out PortStatus message with Port state as LIND_DOWN, this issue doesn't impact on the datapath forwarding. This change is a workaround to ensure Pod's OpenFlow entries are installed as long as the OpenFlow port is allocated. Signed-off-by: Wenying Dong <[email protected]>
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.
LGTM
/test-all |
/test-windows-all |
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 the quick fix.
/test-windows-e2e |
1 similar comment
/test-windows-e2e |
/test-windows-all |
/test-windows-conformance |
The Windows e2e failure is because a "coredns" Pod desired in the test case is not running as expected, which fails because the required image The Windows conformance test is failed with case |
…trea-io#6889) On Windows, OVS has an issue which doesn't correctly update the port status after an OpenFlow port is successfully installed. So OVS may send out PortStatus message with Port state as LIND_DOWN, this issue doesn't impact on the datapath forwarding. This change is a workaround to ensure Pod's OpenFlow entries are installed as long as the OpenFlow port is allocated. Signed-off-by: Wenying Dong <[email protected]>
) (#6893) On Windows, OVS has an issue which doesn't correctly update the port status after an OpenFlow port is successfully installed. So OVS may send out PortStatus message with Port state as LIND_DOWN, this issue doesn't impact on the datapath forwarding. This change is a workaround to ensure Pod's OpenFlow entries are installed as long as the OpenFlow port is allocated. Signed-off-by: Wenying Dong <[email protected]>
On Windows, OVS has an issue which doesn't correctly update the port status after an OpenFlow port is successfully installed. So OVS may send out PortStatus message with Port state as LINK_DOWN, this issue doesn't impact on the datapath forwarding.
This change is a workaround to ensure Pod's OpenFlow entries are installed as long as the OpenFlow port is allocated.
Fix: #6888