Bug 2073411

Summary: Not possible to reach loadBalancerIP from other nodes when externalTrafficPolicy = local
Product: OpenShift Container Platform Reporter: Jitendra Pradhan <jpradhan>
Component: NetworkingAssignee: Surya Seetharaman <surya>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: anusaxen, bzvonar, eglottma, fbaudin, fpaoline, kkarampo, lmohanty, mfojtik, surya, tkondvil, wking
Version: 4.10Keywords: Regression, Upgrades
Target Milestone: ---   
Target Release: 4.10.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-11 10:31:47 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:
Bug Depends On: 2072134    
Bug Blocks:    

Comment 7 Surya Seetharaman 2022-04-13 16:55:17 UTC
Engineering has the fix already: https://github.com/ovn-org/ovn-kubernetes/pull/2918/commits/9dcd82209c97efbe817fa0778e2a7c0dc599378a. Will clean up the PR and prioritize on getting it merged asap!

Comment 35 errata-xmlrpc 2022-05-11 10:31:47 UTC
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 (OpenShift Container Platform 4.10.13 bug fix 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.


Comment 37 W. Trevor King 2022-05-18 23:10:53 UTC
[1] is 4.10.13 landing in stable-4.10.  But our general commitments are [2]:

  When an update recommendation is supported, it remains supported for the life of 4.10, even if the update recommendation is later dropped or made conditional.

  Red Hat will eventually provide supported update paths from any supported release in the fast-4.10 or stable-4.10 channels to the latest release in 4.10.z, although there can be delays while safe paths away from troubled releases are constructed and verified.

which does not include a commitment that we will recommend updates into 4.10.13 in stable-4.10.  Because if we had seen or heard about a serious stability issue on 4.10.13, we might have stopped recommending updates to 4.10.13 before 4.10.13 made it into stable-4.10.

And also, folks who are tired of waiting for an update recommendation in stable channels are free to use fast channels, which are also fully supported [3].

[1]: https://github.com/openshift/cincinnati-graph-data/pull/1907#event-6631933724
[2]: https://docs.openshift.com/container-platform/4.10/updating/understanding-upgrade-channels-release.html#upgrade-version-paths_understanding-upgrade-channels-releases
[3]: https://docs.openshift.com/container-platform/4.10/updating/understanding-upgrade-channels-release.html#fast-version-channel_understanding-upgrade-channels-releases