Bug 1788135 - Authentication operator is degraded in IPv6 cluster
Summary: Authentication operator is degraded in IPv6 cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.4.0
Assignee: Stefan Schimanski
QA Contact: scheng
URL:
Whiteboard:
Depends On:
Blocks: 1788161 1788526
TreeView+ depends on / blocked
 
Reported: 2020-01-06 14:15 UTC by Pawel Krupa
Modified: 2020-05-04 11:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1788161 1788526 (view as bug list)
Environment:
Last Closed: 2020-05-04 11:22:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
must gather (18.92 MB, application/gzip)
2020-01-06 14:15 UTC, Pawel Krupa
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-authentication-operator pull 231 0 None closed Bug 1788135: Fix IPv6 Support 2020-07-14 05:49:10 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:22:40 UTC

Internal Links: 1788136

Description Pawel Krupa 2020-01-06 14:15:27 UTC
Created attachment 1650118 [details]
must gather

Description of problem:
Authentication operator is degraded causing oauth-proxies to fail

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-18-145749-ipv6.1

How reproducible:
Always

Steps to Reproduce:
1. Start an IPv6 cluster


Actual results:
Installation fails with following message:

```
DEBUG Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, console 
DEBUG Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, console 
DEBUG Still waiting for the cluster to initialize: Working towards 4.3.0-0.nightly-2019-12-18-145749-ipv6.1: 100% complete 
DEBUG Still waiting for the cluster to initialize: Some cluster operators are still updating: authentication, console 
ERROR Cluster operator authentication Degraded is True with RouteHealthDegradedFailedGet: RouteHealthDegraded: failed to GET route: net/http: TLS handshake timeout 
INFO Cluster operator authentication Progressing is Unknown with NoData:  
INFO Cluster operator authentication Available is Unknown with NoData:  
INFO Cluster operator console Progressing is True with SyncLoopRefreshProgressingInProgress: SyncLoopRefreshProgressing: Working toward version 4.3.0-0.nightly-2019-12-18-145749-ipv6.1 
INFO Cluster operator console Available is False with DeploymentAvailableInsufficientReplicas: DeploymentAvailable: 0 pods available for console deployment 
INFO Cluster operator insights Disabled is False with :  
FATAL failed to initialize the cluster: Some cluster operators are still updating: authentication, console
```


Expected results:
Installation succeeds and operator is not degraded


Additional info:

Comment 2 Hongan Li 2020-01-08 02:30:01 UTC
Hi Dan, seems the fix PR is for authentication operator instead of ingress. Do you think should update component to Auth?

Comment 5 errata-xmlrpc 2020-05-04 11:22:02 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, 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:0581


Note You need to log in before you can comment on or make changes to this bug.