Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 6. Downgrading OpenShift

6.1. Overview
Link kopieren

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.6 to 3.5 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
Link kopieren

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/etcd/openshift-backup-pre-upgrade-<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/sysconfig/atomic-openshift-master-api
/etc/sysconfig/atomic-openshift-master-controller
/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
Link kopieren

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. 

# systemctl stop atomic-openshift-master-api 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
Link kopieren

  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-api \
    atomic-openshift-master-controllers \
    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
Link kopieren

Both OpenShift Container Platform 3.5 and 3.6 require Docker 1.12, so Docker does not need to be downgraded.

6.6. Reinstalling RPMs
Link kopieren

Disable the OpenShift Container Platform 3.6 repositories, and re-enable the 3.5 repositories: 

# subscription-manager repos \
    --disable=rhel-7-server-ose-3.6-rpms \
    --enable=rhel-7-server-ose-3.5-rpms
Copy to Clipboard Toggle word wrap

On each master, install the following packages: 

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

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

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. Restoring etcd
Link kopieren

See Backup and Restore.

6.8. Bringing OpenShift Container Platform Services Back Online
Link kopieren

See Backup and Restore.

6.9. Verifying the Downgrade
Link kopieren

  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.5.5.31",
# oc get -n default dc/router -o json | grep \"image\"
    "image": "openshift3/ose-haproxy-router:v3.5.5.31",
    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
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat