Red Hat SummitThis documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 4. Downgrading OpenShift
4.1. Overview
Following an OpenShift Enterprise upgrade, it may be desirable in extreme cases to downgrade your cluster to a previous version. The following sections outline the required steps for each system in a cluster to perform such a downgrade for the OpenShift Enterprise 3.2 to 3.1 downgrade path.
These steps are currently only supported for RPM-based installations of OpenShift Enterprise and assumes downtime of the entire cluster.
For the OpenShift Enterprise 3.1 to 3.0 downgrade path, see the OpenShift Enterprise 3.1 documentation, which has modified steps.
4.2. Verifying Backups
The Ansible playbook used during the upgrade process should have created a backup of the master-config.yaml file and the etcd data directory. Ensure these exist on your masters and etcd members:
/etc/origin/master/master-config.yaml.<timestamp> /var/lib/origin/etcd-backup-<timestamp>
/etc/origin/master/master-config.yaml.<timestamp>
/var/lib/origin/etcd-backup-<timestamp>Also, back up the node-config.yaml file on each node (including masters, which have the node component on them) with a timestamp:
/etc/origin/node/node-config.yaml.<timestamp>
/etc/origin/node/node-config.yaml.<timestamp>If you use a separate etcd cluster instead of a single embedded etcd instance, the backup is likely created on all etcd members, though only one is required for the recovery process. You can run a separate etcd instance that is co-located with your master nodes.
The RPM downgrade process in a later step should create .rpmsave backups of the following files, but it may be a good idea to keep a separate copy regardless:
/etc/sysconfig/atomic-openshift-master /etc/etcd/etcd.conf
/etc/sysconfig/atomic-openshift-master
/etc/etcd/etcd.conf - 1
- Only required if using a separate etcd cluster.
4.3. Shutting Down the Cluster
On all masters, nodes, and etcd members, if you use a separate etcd cluster that runs on different nodes, ensure the relevant services are stopped.
On the master in a single master cluster:
systemctl stop atomic-openshift-master
# systemctl stop atomic-openshift-masterOn each master in a multi-master cluster:
systemctl stop atomic-openshift-master-api systemctl stop atomic-openshift-master-controllers
# systemctl stop atomic-openshift-master-api
# systemctl stop atomic-openshift-master-controllersOn all master and node hosts:
systemctl stop atomic-openshift-node
# systemctl stop atomic-openshift-nodeOn any etcd hosts for a separate etcd cluster:
systemctl stop etcd
# systemctl stop etcd4.4. Removing RPMs
On all masters, nodes, and etcd members, if you use a separate etcd cluster that runs on different nodes, remove the following packages:
If you use a separate etcd cluster, also remove the etcd package:
yum remove etcd
# yum remove etcd
If using the embedded etcd, leave the etcd package installed. It is required for running the etcdctl command to issue operations in later steps.
4.5. Downgrading Docker
OpenShift Enterprise 3.2 requires Docker 1.9.1 and also supports Docker 1.10.3, however OpenShift Enterprise 3.1 requires Docker 1.8.2.
Downgrade to Docker 1.8.2 on each host using the following steps:
Remove all local containers and images on the host. Any pods backed by a replication controller will be recreated.
WarningThe following commands are destructive and should be used with caution.
Delete all containers:
docker rm $(docker ps -a -q)
# docker rm $(docker ps -a -q)Copy to Clipboard Copied! Toggle word wrap Toggle overflow Delete all images:
docker rmi $(docker images -q)
# docker rmi $(docker images -q)Copy to Clipboard Copied! Toggle word wrap Toggle overflow Use
yum swap(instead ofyum downgrade) to install Docker 1.8.2:yum swap docker-* docker-*1.8.2 sed -i 's/--storage-opt dm.use_deferred_deletion=true//' /etc/sysconfig/docker-storage systemctl restart docker
# yum swap docker-* docker-*1.8.2 # sed -i 's/--storage-opt dm.use_deferred_deletion=true//' /etc/sysconfig/docker-storage # systemctl restart dockerCopy to Clipboard Copied! Toggle word wrap Toggle overflow You should now have Docker 1.8.2 installed and running on the host. Verify with the following:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.6. Reinstalling RPMs
Disable the OpenShift Enterprise 3.3 repositories, and re-enable the 3.2 repositories:
subscription-manager repos \
--disable=rhel-7-server-ose-3.3-rpms \
--enable=rhel-7-server-ose-3.2-rpms
# subscription-manager repos \
--disable=rhel-7-server-ose-3.3-rpms \
--enable=rhel-7-server-ose-3.2-rpmsOn each master, install the following packages:
On each node, install the following packages:
yum install atomic-openshift \
atomic-openshift-node \
openvswitch \
atomic-openshift-sdn-ovs \
tuned-profiles-atomic-openshift-node
# yum install atomic-openshift \
atomic-openshift-node \
openvswitch \
atomic-openshift-sdn-ovs \
tuned-profiles-atomic-openshift-nodeIf you use a separate etcd cluster, install the following package on each etcd member:
yum install etcd
# yum install etcd4.7. Restoring etcd
See Backup and Restore.
4.8. Bringing OpenShift Enterprise Services Back Online
See Backup and Restore.
4.9. Verifying the Downgrade
To verify the downgrade, first check that all nodes are marked as Ready:
oc get nodes
# oc get nodes
NAME STATUS AGE
master.example.com Ready,SchedulingDisabled 165d
node1.example.com Ready 165d
node2.example.com Ready 165dThen, 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\" oc get -n default dc/router -o json | grep \"image\"
# oc get -n default dc/docker-registry -o json | grep \"image\"
"image": "openshift3/ose-docker-registry:v3.1.1.6",
# oc get -n default dc/router -o json | grep \"image\"
"image": "openshift3/ose-haproxy-router:v3.1.1.6",
You can use the diagnostics tool on the master to look for common issues and provide suggestions. In OpenShift Enterprise 3.1, the oc adm diagnostics tool is available as openshift ex diagnostics:
openshift ex diagnostics
# openshift ex diagnostics
...
[Note] Summary of diagnostics execution:
[Note] Completed with no errors or warnings seen.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}