| Summary: | Got "x509: certificate has expired or is not yet valid" after running one day | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
| Component: | Master | Assignee: | David Eads <deads> |
| Status: | CLOSED ERRATA | QA Contact: | Jian Zhang <jiazha> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | aos-bugs, chezhang, deads, dyan, jfan, jokerman, mmccomas, sponnaga, zitang |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 4.1.0 | ||
| 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: | 2019-06-04 10:42:08 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: | |
|
Description
Jian Zhang
2019-01-23 05:36:24 UTC
This is a known problem in the beta that was fixed over the course of several pulls. To unstick yourself, try `oc -n openshift-apiserver delete pods --all`. Hopefully I found the right closure reason. David, No, I don't think so. As I described in "Additional info:" section, the issue still exists after `oc -n openshift-apiserver delete pods --all`. Still get the errors after restarted the apiserver pods. [core@ip-10-0-14-64 ~]$ oc get pods -n openshift-apiserver NAME READY STATUS RESTARTS AGE apiserver-2rftt 1/1 Running 0 2h apiserver-gwrgb 1/1 Running 0 2h apiserver-zn8c8 1/1 Running 0 2h And, seems like the errors: "x509: certificate has expired or is not yet valid, x509: certificate has expired or is not yet valid" is different from we reported bug 1665842 for Beta-1. So reopen it. Please set the status to the "ON_QA" if you fixed it. I don't see this in master I didn't hit issue again, it works as expected by now, verify it. Details as below: [jzhang@dhcp-140-18 ocp-14]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-13-204401 True False 26h Cluster version is 4.0.0-0.nightly-2019-02-13-204401 [jzhang@dhcp-140-18 ocp-14]$ oc whoami system:admin [jzhang@dhcp-140-18 ocp-14]$ oc project openshift-apiserver Now using project "openshift-apiserver" on server "https://jian-14-api.qe.devcluster.openshift.com:6443" 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:0758 |