Bug 2072780
| Summary: | OVN kube-master does not clear NetworkUnavailableCondition on GCP BYOH Windows node | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Aravindh Puthiyaparambil <aravindh> | |
| Component: | Networking | Assignee: | Jacob Tanenbaum <jtanenba> | |
| Networking sub component: | ovn-kubernetes | QA Contact: | Ronnie Rasouli <rrasouli> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | medium | |||
| Priority: | medium | CC: | anbhat, arnaik, jfrancoa, jtanenba, mapandey, rteague | |
| Version: | 4.10 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.11.0 | |||
| Hardware: | x86_64 | |||
| OS: | Windows | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2079546 (view as bug list) | Environment: | ||
| Last Closed: | 2022-08-10 11:04:00 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2079546 | |||
|
Description
Aravindh Puthiyaparambil
2022-04-06 23:41:00 UTC
I suspect what is happening is that the Windows node is being considered a NoHostSubnet node [1] and because of which oc.addNode [2] never gets called on it and as a result oc.clearInitialNodeNetworkUnavailableCondition() never gets called for the Windows node either. WDYT? [1] https://github.com/openshift/ovn-kubernetes/blob/50f9cb61c82697186a9844c4fffab093c00fbe5a/go-controller/pkg/ovn/ovn.go#L1113 [2] https://github.com/openshift/ovn-kubernetes/blob/50f9cb61c82697186a9844c4fffab093c00fbe5a/go-controller/pkg/ovn/ovn.go#L1122 [3] https://github.com/openshift/ovn-kubernetes/blob/50f9cb61c82697186a9844c4fffab093c00fbe5a/go-controller/pkg/ovn/master.go#L1119 I created an upstream issue [1] and a potential fix [2] [1] https://github.com/ovn-org/ovn-kubernetes/issues/2901 [2] https://github.com/ovn-org/ovn-kubernetes/pull/2902 This has been fixed upstream [1] [1] https://github.com/ovn-org/ovn-kubernetes/pull/2870 *** Bug 2058912 has been marked as a duplicate of this bug. *** We tried to validate this issue but the NetworkUnavailable options is still appearing as True:
"conditions": [
{
"lastHeartbeatTime": null,
"lastTransitionTime": "2022-05-05T12:54:32Z",
"message": "Node created without a route",
"reason": "NoRouteCreated",
"status": "True",
"type": "NetworkUnavailable"
},
I made sure that the patch from @jtanenba would be present in the ovn-kubernetes submodule before building the wmco-index image, however I still see the same effect.
I'm attaching some of the logs from ovnkube-master and wmco. If you need any other logs, please let me know. I also have a reproducer available in case you would like to jump in (ping me in slack @jfrancoa)
"version": "5.0.0-f409122"
"conditions": [
{
"lastHeartbeatTime": null,
"lastTransitionTime": "2022-05-08T18:12:07Z",
"message": "ovn-kube cleared kubelet-set NoRouteCreated",
"reason": "RouteCreated",
"status": "False",
"type": "NetworkUnavailable"
},
"conditions": [
{
"lastHeartbeatTime": null,
"lastTransitionTime": "2022-05-08T18:12:07Z",
"message": "ovn-kube cleared kubelet-set NoRouteCreated",
"reason": "RouteCreated",
"status": "False",
"type": "NetworkUnavailable"
},
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |