2.7. Verifying the upgrade
Ensure that:
- The cluster is healthy.
- The master, node, and etcd services or static pods are running well.
-
The OpenShift Container Platform,
docker-registry, and router versions are correct. - The original applications are still available, and new application can be created.
-
Running
oc adm diagnosticsproduces no errors.
To verify the upgrade:
Check that all nodes are marked as Ready:
# oc get nodes NAME STATUS ROLES AGE VERSION master1.example.com Ready master 47d v1.11.0+d4cacc0 master2.example.com Ready master 47d v1.11.0+d4cacc0 master3.example.com Ready master 47d v1.11.0+d4cacc0 infra-node1.example.com Ready infra 47d v1.11.0+d4cacc0 infra-node2.example.com Ready infra 47d v1.11.0+d4cacc0 node1.example.com Ready compute 47d v1.11.0+d4cacc0 node2.example.com Ready compute 47d v1.11.0+d4cacc0
Verify that the static pods for the control plane are running:
# oc get pods -n kube-system NAME READY STATUS RESTARTS AGE master-api-master1.example.com 1/1 Running 4 1h master-controllers-master1.example.com 1/1 Running 3 1h master-etcd-master1.example.com 1/1 Running 6 5d [...]
Verify that you are running the expected versions of the docker-registry and router images, if deployed:
# oc get -n default dc/docker-registry -o json | grep \"image\" "image": "openshift3/ose-docker-registry:v3.11", # oc get -n default dc/router -o json | grep \"image\" "image": "openshift3/ose-haproxy-router:v3.11",Use the diagnostics tool on the master to look for common issues:
# oc adm diagnostics ... [Note] Summary of diagnostics execution: [Note] Completed with no errors or warnings seen.
