Description of problem: After upgrade rpm installed ocp to v3.10, found that 1)etcd was not run as static pod. 2) atomic-openshift-master was still updated to 3.10 which should be dropped. # oc get all -n kube-system NAME READY STATUS RESTARTS AGE pod/master-api-qe-jliu-rpm39-master-etcd-1 1/1 Running 1 1h pod/master-controllers-qe-jliu-rpm39-master-etcd-1 1/1 Running 1 1h systemctl status etcd.service ● etcd.service - Etcd Server Loaded: loaded (/usr/lib/systemd/system/etcd.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2018-04-23 00:30:52 EDT; 3h 24min ago Main PID: 15320 (etcd) Version-Release number of the following components: openshift-ansible-3.10.0-0.27.0.git.0.abed3b7.el7.noarch How reproducible: always Steps to Reproduce: 1. rpm install ocp v3.9 2. enable v3.10 ose repos and upgrade above ocp 3. Actual results: Etcd was not run as static pod. Expected results: Master api/controllers and etcd were run as static pod after upgrade. Additional info: Please attach logs from ansible-playbook with the -vvv flag
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