Bug 1571054
Summary: | Etcd was not run as static pod after upgrade rpm ocp | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
Component: | Cluster Version Operator | Assignee: | Michael Gugino <mgugino> |
Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.10.0 | CC: | aos-bugs, jokerman, mgugino, mmccomas, wmeng, wsun |
Target Milestone: | --- | ||
Target Release: | 3.10.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: | 2018-07-30 19:13:42 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
liujia
2018-04-24 02:45:45 UTC
Etcd need to be run as a static pod is required for control plane in v3.10. Need this bug fixed asap. PR Submitted: https://github.com/openshift/openshift-ansible/pull/8206 @ QA owner: The PR has been merged in 3.10.0-0.33.0 , please check. Blocked by bz1575507. Delete this testblocker keyword first. Verified on atomic-openshift-3.10.0-0.38.0.git.0.ae093fb.el7.x86_64 # oc get pod -n kube-system NAME READY STATUS RESTARTS AGE master-api-qe-jliu-r39a-master-etcd-1 1/1 Running 1 45m master-controllers-qe-jliu-r39a-master-etcd-1 1/1 Running 1 45m master-etcd-qe-jliu-r39a-master-etcd-1 1/1 Running 0 50m # ls -la /etc/origin/node/pods/ total 16 drwx------. 2 root root 68 May 14 02:41 . drwx------. 4 root root 4096 May 14 02:32 .. -rw-------. 1 root root 1477 May 14 02:41 apiserver.yaml -rw-------. 1 root root 1253 May 14 02:41 controller.yaml -rw-------. 1 root root 922 May 14 02:34 etcd.yaml 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-2018:1816 |