You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/rhel-compute-updating.adoc
+37-19Lines changed: 37 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,26 +2,30 @@
2
2
//
3
3
// * updating/updating-cluster-rhel-compute.adoc
4
4
5
-
[id="rhel-compute-updating_{context}"]
6
-
= Updating RHEL compute machines in your cluster
5
+
[id="rhel-compute-updating-minor_{context}"]
6
+
= Updating {op-system-base} compute machines in your cluster
7
7
8
-
After you update your cluster, you must update the Red Hat Enterprise Linux (RHEL)
9
-
compute machines in your cluster.
8
+
After you update your cluster, you must update the {op-system-base-full} compute machines in your cluster.
9
+
10
+
[IMPORTANT]
11
+
====
12
+
Because only {op-system-base-full} version 7.9 or later is supported for worker (compute) machines, you must not upgrade the {op-system-base} worker machines to version 8.
13
+
====
14
+
15
+
You can also update your compute machines to another minor version of {product-title} if you are using {op-system-base} as the operating system. You do not need to exclude any RPM packages from {op-system-base} when performing a minor version update.
10
16
11
17
.Prerequisites
12
18
13
19
* You updated your cluster.
14
20
+
15
21
[IMPORTANT]
16
22
====
17
-
Because the RHEL machines require assets that are generated by the cluster to
18
-
complete the update process, you must update the cluster before you update
19
-
the RHEL compute machines in it.
23
+
Because the {op-system-base} machines require assets that are generated by the cluster to complete the update process, you must update the cluster before you update the {op-system-base} worker machines in it.
20
24
====
21
25
22
-
* You have access to the machine that you used to add the RHEL compute machines
23
-
cluster. You must have access to the `hosts` Ansible inventory file that defines
24
-
your RHEL machines and the `upgrade` playbook.
26
+
* You have access to the local machine that you used to add the {op-system-base} compute machines to your cluster. You must have access to the `hosts` Ansible inventory file that defines your {op-system-base} machines and the `upgrade` playbook.
27
+
28
+
* For updates to a minor version, the RPM repository is using the same version of {product-title} that is running on your cluster.
25
29
26
30
.Procedure
27
31
@@ -54,7 +58,7 @@ You must not enable firewalld later. If you do, you cannot access {product-title
54
58
# yum update openshift-ansible openshift-clients
55
59
----
56
60
57
-
.. On each RHEL compute node, update the required repositories:
61
+
.. On each {op-system-base} compute node, update the required repositories:
58
62
+
59
63
[source,terminal]
60
64
----
@@ -64,8 +68,8 @@ You must not enable firewalld later. If you do, you cannot access {product-title
64
68
--enable=rhel-7-server-optional-rpms
65
69
----
66
70
67
-
. Update a RHEL worker machine:
68
-
.. Review the current node status to determine which RHEL worker to update:
71
+
. Update a {op-system-base} worker machine:
72
+
.. Review the current node status to determine which {op-system-base} worker to update:
Note which machine has the `NotReady,SchedulingDisabled` status.
89
93
90
-
.. Review your Ansible inventory file at `/<path>/inventory/hosts`
91
-
and update its contents so that only the machine with the `NotReady,SchedulingDisabled` status is listed in the `[workers]` section, as shown in the following example:
94
+
.. Review your Ansible inventory file at `/<path>/inventory/hosts` and update its contents so that only the machine with the `NotReady,SchedulingDisabled` status is listed in the `[workers]` section, as shown in the following example:
92
95
+
93
96
----
94
97
[all:vars]
@@ -114,10 +117,14 @@ $ cd /usr/share/ansible/openshift-ansible
. Optional: Update the operating system packages that were not updated by the `upgrade` playbook. To update packages that are not on {product-version}, use the following command:
149
+
+
150
+
[source,terminal]
151
+
----
152
+
# yum update
153
+
----
154
+
+
155
+
[NOTE]
156
+
====
157
+
You do not need to exclude RPM packages if you are using the same RPM repository that you used when you installed {product-version}.
0 commit comments