Bug 1872058

Summary:	Ingress Operator improperly sets IBM Cloud LB annotations
Product:	OpenShift Container Platform	Reporter:	Daneyon Hansen <dhansen>
Component:	Networking	Assignee:	Daneyon Hansen <dhansen>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs, cewong
Version:	4.6
Target Milestone:	---
Target Release:	4.6.0
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-10-27 16:32: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:

Description Daneyon Hansen 2020-08-24 22:39:15 UTC

Description of problem:
Ingress Operator does not properly set IBM Cloud public annotation.

Version-Release number of selected component (if applicable):
4.6

How reproducible:
Always

Steps to Reproduce:
1. Install cluster with IBM provider.
2. Install fails due to ingress operator setting both private and public annotations.

Actual results:
Failed install.

Expected results:
Successful install.

Additional info:

Comment 1 Daneyon Hansen 2020-08-26 19:10:11 UTC

*** Bug 1872057 has been marked as a duplicate of this bug. ***

Comment 5 Cesar Wong 2020-09-01 17:14:24 UTC

Verified on 4.6.0-0.nightly-2020-08-31-194600 with ROKS-style cluster

Comment 6 Hongan Li 2020-09-02 08:45:59 UTC

Thank you @Cesar. Also tested on other cloud platform and no regression issue. so moving to verified.

Comment 8 errata-xmlrpc 2020-10-27 16:32:00 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.6 GA Images), 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:4196