Bug 1688802
| Summary: | openshift-apiserver clusteroperator unavailable on clean install | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Justin Pierce <jupierce> | ||||
| Component: | Networking | Assignee: | Casey Callendrello <cdc> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, maszulik, mmccomas, trankin, weliang | ||||
| Target Milestone: | --- | Keywords: | DeliveryBlocker, OpsBlocker | ||||
| Target Release: | 4.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-07-04 09:01:22 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: | |||||||
| Attachments: |
|
||||||
|
Description
Justin Pierce
2019-03-14 13:43:45 UTC
https://github.com/openshift/origin/pull/22302 is the potential fix. I've just spin up a cluster using 4.0.0-0.alpha-2019-03-15-093013 and it seems just fine. If the problem persist, feel free to reopen. Checked above attachment, it included CrashLoopBackOff info due to readiness failure: $ oc -n openshift-apiserver get all NAME READY STATUS RESTARTS AGE pod/apiserver-pt7b4 0/1 CrashLoopBackOff 107 9h pod/apiserver-r7s46 0/1 CrashLoopBackOff 108 9h pod/apiserver-sx6j4 0/1 CrashLoopBackOff 107 9h I never hit such failure after in testing fresh installation with builds, no matter including above PR (latest build 4.0.0-0.nightly-2019-03-15-063749) or not. What I hit about the clusteroperator is another issue: cert bug 1688820 (duplicating bug 1688147 / bug 1688503). Per above PR, it relates to networking. Suggest move this bug to Networking component for better verification. Hmm, let me move it. If wrong, pls correct. Testing passed in a new installation with v4.0.0-0.177.0. [root@dhcp-41-193 openshift-client]# oc get all -n openshift-apiserver NAME READY STATUS RESTARTS AGE pod/apiserver-dwltt 1/1 Running 0 6m6s pod/apiserver-mjhlj 1/1 Running 0 5m43s pod/apiserver-p6sw7 1/1 Running 0 6m56s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/api ClusterIP 172.30.114.184 <none> 443/TCP 10m NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/apiserver 3 3 3 3 3 node-role.kubernetes.io/master= 10m [root@dhcp-41-193 openshift-client]# oc version oc v4.0.0-0.177.0 kubernetes v1.12.4+6a9f178753 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://api.weliang.qe.devcluster.openshift.com:6443 kubernetes v1.12.4+6d3ea30 [root@dhcp-41-193 openshift-client]# 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-2019:1635 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |