Bug 1800338
Summary: | need to backport changes for adding LB for IBMCloud | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | ayma <ayma> |
Component: | Networking | Assignee: | Dan Mace <dmace> |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | anli, aos-bugs, cewong, decarr, dmace, hongli |
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Target Release: | 4.3.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | IBMROKS | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1800337 | Environment: | |
Last Closed: | 2020-03-10 23:53:52 UTC | Type: | --- |
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: | 1800337 | ||
Bug Blocks: |
Description
ayma@us.ibm.com
2020-02-06 21:41:25 UTC
*** Bug 1796140 has been marked as a duplicate of this bug. *** OCP QE has verified this with 4.3.0-0.nightly-2020-02-16-175702 and no regression. waiting for the feedback from IBM ROKS team. Failed to verify this in 4.3.0-0.nightly-2020-02-16-175702. The cluster ingress EndpointPublishingStrategy is not getting set to type 'LoadBalancerService' which then prevents the load balancer service type from being created. @cesar, Could you try this payload quay.io/openshift-release-dev/ocp-release:4.3.3-x86_64? The Advisory The follow-up fix PR https://github.com/openshift/cluster-ingress-operator/pull/362 has not been merged, so maybe needn't to give a try with the 4.3.3 payload. @hongli, Thanks. I will ask Art to drop this bug from Advisory. Verified this is working with 4.3.0-0.nightly-2020-02-26-221811 Thank you Cesar. Verified with 4.3.0-0.nightly-2020-02-26-221811 and no regression on other platforms. moving to verified. 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, 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:0676 |