Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1769882

Summary:	[GCP] the DNS record for the wildcard apps is not updated after recreating the default ingresscontroller
Product:	OpenShift Container Platform	Reporter:	Daneyon Hansen <dhansen>
Component:	Networking	Assignee:	Andrew McDermott <amcdermo>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	medium
Priority:	high	CC:	aos-bugs, dmace, hongli, mfojtik, sttts
Version:	4.3.0
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1766141	Environment:
Last Closed:	2020-05-28 15:28:39 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:	1766141
Bug Blocks:

Comment 1 Daneyon Hansen 2020-01-27 17:28:38 UTC

This bug was fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1766141 by https://github.com/openshift/cluster-ingress-operator/pull/320. The bug can not be backported to 4.2 (k8s v1.15) without the apiserver adding FeatureGate support for serviceLoadBalancerFinalizer. Reassigning to the apiserver team to see if this warrants adding the FeatureGate. If so, existence checking can be added for the finalizer to fix this issue without requiring an upgrade to 4.3.
.

Comment 2 Daneyon Hansen 2020-01-27 21:08:55 UTC

Additional background can be found in https://bugzilla.redhat.com/show_bug.cgi?id=1766141#c11.

Comment 3 Michal Fojtik 2020-05-12 10:45:11 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

As such, we're marking this bug as "LifecycleStale" and decreasing the severity. 

If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 4 Stefan Schimanski 2020-05-12 12:26:13 UTC

4.2 was 1.14. The feature gate did not even exist. This would mean a carry patch for origin, to be created & maintained by edge team.

Comment 5 Andrew McDermott 2020-05-28 15:28:39 UTC

(In reply to Stefan Schimanski from comment #4)
> 4.2 was 1.14. The feature gate did not even exist. This would mean a carry
> patch for origin, to be created & maintained by edge team.

I read this bug as a fix for 4.2 specifically. 

As 4.2 will soon be going into end of maintenance (once 4.5 ships) I'm closing this.

Comment 6 Red Hat Bugzilla 2023-09-15 01:28:51 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days