Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 6. Downgrading OpenShift

6.1. Overview
링크 복사

Following an OpenShift Container Platform 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 Container Platform 3.3 to 3.2 downgrade path.

Warning

These steps are currently only supported for RPM-based installations of OpenShift Container Platform and assumes downtime of the entire cluster.

6.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>
Copy to Clipboard Toggle word wrap

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>
Copy to Clipboard Toggle word wrap

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
1
Copy to Clipboard Toggle word wrap
1
Only required if using a separate etcd cluster.

6.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
Copy to Clipboard Toggle word wrap

On each master in a multi-master cluster: 

# systemctl stop atomic-openshift-master-api
# systemctl stop atomic-openshift-master-controllers
Copy to Clipboard Toggle word wrap

On all master and node hosts: 

# systemctl stop atomic-openshift-node
Copy to Clipboard Toggle word wrap

On any etcd hosts for a separate etcd cluster: 

# systemctl stop etcd
Copy to Clipboard Toggle word wrap

6.4. Removing RPMs
링크 복사

  1. The *-excluder packages add entries to the exclude directive in the host’s /etc/yum.conf file when installed. Run the following command on each host to remove the atomic-openshift-* and docker packages from the exclude list: 

    # atomic-openshift-excluder unexclude
# atomic-openshift-docker-excluder unexclude
    Copy to Clipboard Toggle word wrap

  2. On all masters, nodes, and etcd members, if you use a separate etcd cluster that runs on different nodes, remove the following packages: 

    # yum remove atomic-openshift \
    atomic-openshift-clients \
    atomic-openshift-node \
    atomic-openshift-master \
    openvswitch \
    atomic-openshift-sdn-ovs \
    tuned-profiles-atomic-openshift-node\
    atomic-openshift-excluder \
    atomic-openshift-docker-excluder
    Copy to Clipboard Toggle word wrap

  3. If you use a separate etcd cluster, also remove the etcd package: 

    # yum remove etcd
    Copy to Clipboard Toggle word wrap

    If using the embedded etcd, leave the etcd package installed. It is required for running the etcdctl command to issue operations in later steps.

6.5. Downgrading Docker
링크 복사

OpenShift Container Platform 3.2 requires Docker 1.9.1 and also supports Docker 1.10.3.

Downgrade to Docker 1.9.1 on each host using the following steps:

  1. Remove all local containers and images on the host. Any pods backed by a replication controller will be recreated.

    Warning

    The following commands are destructive and should be used with caution.

    Delete all containers: 

    # docker rm $(docker ps -a -q)
    Copy to Clipboard Toggle word wrap

    Delete all images: 

    # docker rmi $(docker images -q)
    Copy to Clipboard Toggle word wrap

  2. Use yum swap (instead of yum downgrade) to install Docker 1.9.1: 

    # yum swap docker-* docker-*1.9.1
# sed -i 's/--storage-opt dm.use_deferred_deletion=true//' /etc/sysconfig/docker-storage
# systemctl restart docker
    Copy to Clipboard Toggle word wrap

  3. You should now have Docker 1.9.1 installed and running on the host. Verify with the following: 

    # docker version
Client:
 Version:      1.9.1-el7
 API version:  1.20
 Package Version: docker-1.9.1-10.el7.x86_64
[...]

# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2017-06-21 15:44:20 EDT; 30min ago
[...]
    Copy to Clipboard Toggle word wrap

6.6. Reinstalling RPMs
링크 복사

  1. Disable the OpenShift Container Platform 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
    Copy to Clipboard Toggle word wrap

  2. On each master, install the following packages: 

    # yum install atomic-openshift \
    atomic-openshift-clients \
    atomic-openshift-node \
    atomic-openshift-master \
    openvswitch \
    atomic-openshift-sdn-ovs \
    tuned-profiles-atomic-openshift-node \
    atomic-openshift-excluder \
    atomic-openshift-docker-excluder
    Copy to Clipboard Toggle word wrap

  3. On each node, install the following packages: 

    # yum install atomic-openshift \
    atomic-openshift-node \
    openvswitch \
    atomic-openshift-sdn-ovs \
    tuned-profiles-atomic-openshift-node \
    atomic-openshift-excluder \
    atomic-openshift-docker-excluder
    Copy to Clipboard Toggle word wrap

  4. If you use a separate etcd cluster, install the following package on each etcd member: 

    # yum install etcd
    Copy to Clipboard Toggle word wrap

6.7. Bringing OpenShift Container Platform Services Back Online
링크 복사

See Backup and Restore.

6.8. Verifying the Downgrade
링크 복사

  1. To verify the downgrade, first check that all nodes are marked as Ready: 

    # oc get nodes
NAME                        STATUS                     AGE
master.example.com          Ready,SchedulingDisabled   165d
node1.example.com           Ready                      165d
node2.example.com           Ready                      165d
    Copy to Clipboard Toggle word wrap

  2. Then, 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.2.1.34-5",
# oc get -n default dc/router -o json | grep \"image\"
    "image": "openshift3/ose-haproxy-router:v3.2.1.34-5",
    Copy to Clipboard Toggle word wrap

  3. You can use the diagnostics tool on the master to look for common issues and provide suggestions: 

    # oc adm diagnostics
...
[Note] Summary of diagnostics execution:
[Note] Completed with no errors or warnings seen.
    Copy to Clipboard Toggle word wrap
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat