openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Merge pull request #25014 from openshift-cherrypick-robot/cherry-pick-24773-to-enterprise-4.6

Browse Source 
[enterprise-4.6] OSDOCS-1256, update Updating a cluster by using the web console procedure
This commit is contained in:
Ashley Hardin
2020-08-25 12:20:23 -04:00
committed by GitHub
parent 2a23994fd4 f58da95fbb
commit f16925b3df
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
modules/update-upgrading-web.adoc
View File

@@ -23,7 +23,7 @@ You can find information about available {product-title} advisories and updates
link:https://access.redhat.com/downloads/content/290/ver=4.5/rhel---7/4.5.4/x86_64/product-errata[in the errata section]
of the Customer Portal.
////
update link to 4.4 when available
update link to 4.6 when available
////
.Prerequisites
@@ -33,8 +33,8 @@ update link to 4.4 when available
.Procedure
. From the web console, click *Administration* > *Cluster Settings* and review
the contents of the *Overview* tab.
. For production clusters, ensure that the *CHANNEL* is set to the correct channel for
the contents of the *Details* tab.
. For production clusters, ensure that the *Channel* is set to the correct channel for
ifdef::within[]
the version that you want to update to,
endif::within[]
@@ -47,12 +47,12 @@ such as `stable-{product-version}`.
====
For production clusters, you must subscribe to a stable-* or fast-* channel.
====
** If the *UPDATE STATUS* is not *Updates Available*, you cannot upgrade your
** If the *Update Status* is not *Updates Available*, you cannot upgrade your
cluster.
** The *DESIRED VERSION* indicates the cluster version that your cluster is running
** *Select Channel* indicates the cluster version that your cluster is running
or is updating to.
. Click *Updates Available*, select
. Select
ifdef::within[]
a version to update to,
endif::within[]
@@ -60,15 +60,16 @@ ifdef::between[]
the highest available version
endif::between[]
and click *Update*.
The *UPDATE STATUS* changes to `Updating`, and you can review the progress of
the Operator upgrades on the *Cluster Operators* tab.
The *Update Status* changes to `Update to <product-version> in progress`, and
you can review the progress of the cluster update by watching the progress bars
for the Operators and nodes.
ifdef::between[]
. After the update completes and the Cluster Version Operator refreshes the available updates, check if more updates are available in your current channel.
+
--
** If updates are available, continue to perform updates in the current channel until you can no longer update.
** If no updates are available, change the *CHANNEL* to the stable-* or fast-* channel for the next minor version, and update to the version that you want in that channel.
** If no updates are available, change the *Channel* to the stable-* or fast-* channel for the next minor version, and update to the version that you want in that channel.
--
+
You might need to perform several intermediate updates until you reach the version that you want.
@@ -78,4 +79,5 @@ ifdef::rhel[]
====
When you update a cluster that contains Red Hat Enterprise Linux (RHEL) worker machines, those workers temporarily become unavailable during the update process. You must run the upgrade playbook against each RHEL machine as it enters the `NotReady` state for the cluster to finish updating.
====
endif::rhel[]