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

Bug 1936675

Summary:	Custom ingresscontroller taken precedence over the default ingresscontroller
Product:	OpenShift Container Platform	Reporter:	Miguel Figueiredo Nunes <mnunes>
Component:	Networking	Assignee:	Candace Holman <cholman>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	medium	CC:	amcdermo, aos-bugs, mmasters, sgreene
Version:	4.6.z
Target Milestone:	---
Target Release:	---
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:	2021-04-22 16:50:45 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 Miguel Figueiredo Nunes 2021-03-08 21:33:01 UTC

Description of problem:
Custom ingresscontroller takes precedence over the default ingresscontroller, blocking accessess to default domain, breaking authentication process

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

How reproducible:
Always, when a custom ingresscontroller with a different domain name is used

Steps to Reproduce:
1. Create a custom ingresscontroller
2. Wait to the pods start to run
3. Attempt to authenticate after a logoff

Actual results:
Unable to login again

Expected results:
Able to perform all the cluster operations and be able to use a custom ingresscontroler

Additional info:
- Cluster installed over an OSP
- Pods of the default ingresscontroller in different nodes/labels than those of the custom ingresscontroller

Comment 1 Miciah Dashiel Butler Masters 2021-03-08 23:50:56 UTC

The ingresscontrollers should be independent.  Can you provide the json or yaml definitions of the default and custom ingresscontrollers (`oc -n openshift-ingress-operator get ingresscontrollers -o yaml`)?  

What happens when you attempt to authenticate?  Are you getting an error message?  

As this is OpenStack, the administrator manages the DNS and LB; can you verify that these are properly configured, and provide information on how they are configured?  We should verify that traffic is actually going to the correct ingresscontroller.  

Did the administrator provision separate load balancers for the custom and default ingresscontrollers?  

Can you show the DNS records that the administrator created and sample DNS lookups (using dig) for those records, and provide the configuration of the load balancers (at least their IP addresses)?

Comment 10 Andrew McDermott 2021-04-22 16:50:45 UTC

Based on feedback from the customer this appears to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1886572.

*** This bug has been marked as a duplicate of bug 1886572 ***

Comment 11 Red Hat Bugzilla 2023-09-15 01:33:12 UTC

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