Bug 1891626
Summary: | [Release 4.6] Mutable LoadBalancer Scope | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Dustin Row <drow> |
Component: | Networking | Assignee: | Miciah Dashiel Butler Masters <mmasters> |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | amcdermo, aos-bugs, mmasters, openshift-bugzilla-robot |
Version: | 4.6.z | ||
Target Milestone: | --- | ||
Target Release: | 4.6.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-30 16:45:31 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: | 1891625 | ||
Bug Blocks: |
Description
Dustin Row
2020-10-26 21:28:30 UTC
*** Bug 1892447 has been marked as a duplicate of this bug. *** We'll try to get this backport merged in the upcoming sprint. verified with a cluster (4.6.0-0.ci.test-2020-11-16-084740-ci-ln-qmbvd9t) launched by cluster-bot and passed. # oc -n openshift-ingress-operator patch ingresscontroller/default -p '{"spec":{"endpointPublishingStrategy":{"loadBalancer":{"scope":"Internal"}}}}' --type=merge ingresscontroller.operator.openshift.io/default patched 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.6.6 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. https://access.redhat.com/errata/RHBA-2020:5115 This was a feature backport and I don't believe we should ever set feature backports at high severity. Feature backports go in only once we've cleared the critical period immediately after GA and have enabled upgrades for everyone. Backporting this feature when we did has halted efforts to promote the upgrade. |