Updating clusters

Procedure

1. From the web console, click Administration > Cluster Settings and review the contents of the Overview tab.

   1. For production clusters, ensure that the CHANNEL is set to stable-4.1.

      Important

      For production clusters, you must subscribe to the stable-4.1 channel.

   2. If the UPDATE STATUS is not Updates Available, you cannot upgrade your cluster.
   3. The DESIRED VERSION indicates the cluster version that your cluster is running or is updating to.
2. Click Updates Available, select a version to update to, and click Update. The UPDATE STATUS changes to Updating, and you can review the progress of the Operator upgrades on the Cluster Operators tab.

Procedure

1. Ensure that your cluster is available:

   $ oc get clusterversion
   
   NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
   version   4.1.0     True        False         158m    Cluster version is 4.1.0

2. Review the current update channel information and confirm that your channel is set to stable-4.1:

   $ oc get clusterversion -o json|jq ".items[0].spec"
   
   {
     "channel": "stable-4.1",
     "clusterID": "990f7ab8-109b-4c95-8480-2bd1deec55ff",
     "upstream": "https://api.openshift.com/api/upgrades_info/v1/graph"
   }

   Important

   For production clusters, you must subscribe to the stable-4.1 channel.

3. View the available updates and note the version number of the update that you want to apply:

   $ oc adm upgrade
   
   Cluster version is 4.1.0
   
   Updates:
   
   VERSION IMAGE
   4.1.2   quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b

4. Apply an update:

   • To update to the latest version:

     $ oc adm upgrade --to-latest=true 1

   • To update to a specific version:

     $ oc adm upgrade --to=<version> 1

     1 1

     <version> is the update version that you obtained from the output of the previous command.

5. Review the status of the Cluster Version Operator:

   $ oc get clusterversion -o json|jq ".items[0].spec"
   
   {
     "channel": "stable-4.1",
     "clusterID": "990f7ab8-109b-4c95-8480-2bd1deec55ff",
     "desiredUpdate": {
       "force": false,
       "image": "quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b",
       "version": "4.1.2" 1
     },
     "upstream": "https://api.openshift.com/api/upgrades_info/v1/graph"
   }

   1

   If the version number in the desiredUpdate stanza matches the value that you specified, the update is in progress.

6. Review the cluster version status history to monitor the status of the update. It might take some time for all the objects to finish updating.

   $ oc get clusterversion -o json|jq ".items[0].status.history"
   
   [
     {
       "completionTime": null,
       "image": "quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b",
       "startedTime": "2019-06-19T20:30:50Z",
       "state": "Partial",
       "verified": true,
       "version": "4.1.2"
     },
     {
       "completionTime": "2019-06-19T20:30:50Z",
       "image": "quay.io/openshift-release-dev/ocp-release@sha256:b8307ac0f3ec4ac86c3f3b52846425205022da52c16f56ec31cbe428501001d6",
       "startedTime": "2019-06-19T17:38:10Z",
       "state": "Completed",
       "verified": false,
       "version": "4.1.0"
     }
   ]

   The history contains a list of the most recent versions applied to the cluster. This value is updated when the CVO applies an update. The list is ordered by date, where the newest update is first in the list. Updates in the history have state Completed if the rollout completed and Partial if the update failed or did not complete.

   Important

   If an upgrade fails, the Operator stops and reports the status of the failing component. Rolling your cluster back to a previous version is not supported. If your upgrade fails, contact Red Hat support.

7. After the update completes, you can confirm that the cluster version has updated to the new version:

   $ oc get clusterversion
   
   NAME      VERSION     AVAILABLE   PROGRESSING   SINCE     STATUS
   version   4.1.2       True        False         2m        Cluster version is 4.1.2

Procedure

1. From the web console, click Administration > Cluster Settings and review the contents of the Overview tab.

   1. For production clusters, ensure that the CHANNEL is set to stable-4.1.

      Important

      For production clusters, you must subscribe to the stable-4.1 channel.

   2. If the UPDATE STATUS is not Updates Available, you cannot upgrade your cluster.
   3. The DESIRED VERSION indicates the cluster version that your cluster is running or is updating to.
2. Click Updates Available, select a version to update to, and click Update. The UPDATE STATUS changes to Updating, and you can review the progress of the Operator upgrades on the Cluster Operators tab.

Procedure

1. Stop and disable firewalld on the host:

   # systemctl disable --now firewalld.service

   Note

   You must not enable firewalld later. If you do, you cannot access OpenShift Container Platform logs on the worker.

2. Review your Ansible inventory file at /<path>/inventory/hosts and ensure that all of your compute, or worker, machines are listed in the [workers] section, as shown in the following example:

   [all:vars]
   ansible_user=root
   #ansible_become=True
   
   openshift_kubeconfig_path="~/.kube/config"
   openshift_pull_secret_path="~/pull-secret.txt"
   
   [workers]
   mycluster-worker-0.example.com
   mycluster-worker-1.example.com
   mycluster-worker-2.example.com
   mycluster-worker-3.example.com

   If all of your RHEL compute machines are not listed in the [workers] section, you must move them to that section.

3. Change to the openshift-ansible directory and run the upgrade playbook:

   $ cd /usr/share/ansible/openshift-ansible
   $ ansible-playbook -i /<path>/inventory/hosts playbooks/upgrade.yml 1

   1

   For <path>, specify the path to the Ansible inventory file that you created.