Bug 1993153 - Openshift-apiserver CO unavailable after fresh install of OCP 4.8.2 on VMWare resulting in multiple operators degraded
Summary: Openshift-apiserver CO unavailable after fresh install of OCP 4.8.2 on VMWare...
Keywords:
Status: CLOSED DUPLICATE of bug 1987108
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.8
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Antonio Ojea
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-12 13:36 UTC by Hradayesh Shukla
Modified: 2021-08-30 07:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-30 07:41:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Hradayesh Shukla 2021-08-12 13:36:22 UTC
Description of problem:
- Multiple CO are in degraded state after a fresh UPI install of OCP 4.8.2. 
- Looks similar to BZ #1935539

~~~
NAME                                      VERSION  AVAILABLE  PROGRESSING  DEGRADED  SINCE
authentication                            4.8.2    False      False        True      1d
console                                   4.8.2    False      False        True      18m
monitoring                                         False      True         True      12s
openshift-apiserver                       4.8.2    False      False        False     23h
operator-lifecycle-manager-packageserver  4.8.2    False      False        False     50m
~~~



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


How reproducible:


Steps to Reproduce:
1. Fresh install of OCP 4.8.2 on VMware ESXi [UPI]


Actual results:
- Multiple CO in degraded state since openshift-apiserver is down. 
- Logs prompt: 'APIServicesAvailable: "apps.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)
- Cluster version has this error: Unable to apply 4.8.2: an unknown error has occurred: MultipleErrors 


Expected results:
- Successful installation 



Additional info:
-https://bugzilla.redhat.com/show_bug.cgi?id=1935539

Comment 3 Michal Fojtik 2021-08-12 13:53:23 UTC
** A NOTE ABOUT USING URGENT **

This BZ has been set to urgent severity and priority. When a BZ is marked urgent priority Engineers are asked to stop whatever they are doing, putting everything else on hold.
Please be prepared to have reasonable justification ready to discuss, and ensure your own and engineering management are aware and agree this BZ is urgent. Keep in mind, urgent bugs are very expensive and have maximal management visibility.

NOTE: This bug was automatically assigned to an engineering manager with the severity reset to *unspecified* until the emergency is vetted and confirmed. Please do not manually override the severity.

Comment 6 Antonio Ojea 2021-08-30 07:41:10 UTC
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1987108

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


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