Skip to content

Commit 83a1341

Browse files
sdodsonkalexand-rh
authored andcommitted
Add upgrading to oc 4.9 as a prereq
Move the channel change earlier in the process and note the rollout delay The exact error message would be as follows in case we want to use that. ``` $ oc adm upgrade channel eus-4.10 error: the requested channel "eus-4.10" is not one of the available channels (candidate-4.8, candidate-4.9, eus-4.8, fast-4.8, fast-4.9, stable-4.8, stable-4.9), you must pass --allow-explicit-channel to continue ```
1 parent c727608 commit 83a1341

File tree

1 file changed

+29
-18
lines changed

1 file changed

+29
-18
lines changed

modules/updating-eus-to-eus-upgrade.adoc

Lines changed: 29 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -18,13 +18,14 @@ Following this procedure reduces the total update duration and the number of tim
1818
If your cluster is running a version earlier than {product-title} 4.8.14, you must update to a later 4.8.z version before updating to 4.9.
1919
The update to 4.8.14 or later is necessary to fulfill the minimum version requirements that must be performed without pausing MachineConfigPools.
2020
* Verify that MachineConfigPools is unpaused.
21+
* Update OpenShift CLI `oc` to the target version before each update.
2122
2223
.Procedure
2324

2425
. Upgrade any OLM Operators to versions that are compatible with both versions you are updating to.
2526

26-
. Verify that all MachineConfigPools display a status of `UPDATED` and no MachineConfigPools display a status of `UPDATING`.
27-
View the status of all MachineConfigPools, run the following command:
27+
. Verify that all machine config pools display a status of `UPDATED` and that no machine config pool displays a status of `UPDATING`.
28+
To view the status of all machine config pools, run the following command:
2829
+
2930
[source,terminal]
3031
----
@@ -42,26 +43,36 @@ master rendered-master-ecbb9582781c1091e1c9f19d50cf836c True False
4243
worker rendered-worker-00a3f0c68ae94e747193156b491553d5 True False
4344
----
4445

45-
. Pause the MachineConfigPools you wish to skip reboots on, run the following commands:
46+
. Change to the `eus-4.10` channel. Run the following command:
47+
+
48+
[source,terminal]
49+
----
50+
$ oc adm upgrade channel eus-4.10
51+
----
4652
+
4753
[NOTE]
4854
====
49-
You cannot pause the master pool.
55+
The `oc adm upgrade channel` command is only present in 4.9 or later.
56+
57+
If you receive an error message indicating that `eus-4.10` is not one of the
58+
available channels, this indicates that Red Hat is still rolling out 4.8 to 4.10 EUS upgrades.
59+
This rollout process generally takes 45-90 days starting at the GA date.
5060
====
5161
+
52-
[source,terminal]
53-
----
54-
$ oc patch mcp/worker --type merge --patch '{"spec":{"paused":true}}'
55-
----
5662
57-
. Change to the `eus-4.10` channel, run the following command:
63+
. Pause the machine config pools that you want to skip reboots on. Run the following commands:
64+
+
65+
[NOTE]
66+
====
67+
You cannot pause the master pool.
68+
====
5869
+
5970
[source,terminal]
6071
----
61-
$ oc adm upgrade channel eus-4.10
72+
$ oc patch mcp/worker --type merge --patch '{"spec":{"paused":true}}'
6273
----
6374

64-
. Update to 4.9, run the following command:
75+
. Update to version 4.9. Run the following command:
6576
+
6677
[source,terminal]
6778
----
@@ -75,7 +86,7 @@ $ oc adm upgrade --to-latest
7586
Updating to latest version 4.9.18
7687
----
7788

78-
. Ensure the 4.9 updates are completed successfully retrieve the cluster version, run the following command:
89+
. Ensure that the 4.9 updates completed by reviewing the cluster version. Run the following command:
7990
+
8091
[source,terminal]
8192
----
@@ -90,16 +101,16 @@ NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
90101
version 4.9.18 True False 6m29s Cluster version is 4.9.18
91102
----
92103

93-
. If necessary, upgrade OLM Operators using the Administrator perspective on the web console.
104+
. If necessary, upgrade OLM Operators by using the Administrator perspective on the web console.
94105

95-
. Update to 4.10, run the following command:
106+
. Update to version 4.10. Run the following command:
96107
+
97108
[source,terminal]
98109
----
99110
$ oc adm upgrade --to-latest
100111
----
101112

102-
. Ensure the 4.10 update is completed successfully retrieve the cluster version, run the following command:
113+
. Ensure that the 4.10 update completed by retrieving the cluster version. Run the following command:
103114
+
104115
[source,terminal]
105116
----
@@ -114,7 +125,7 @@ NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
114125
version 4.10.1 True False 6m29s Cluster version is 4.10.1
115126
----
116127

117-
. Unpause all previously paused MachineConfigPools, run the following command:
128+
. Unpause all previously paused machine config pools. Run the following command:
118129
+
119130
[source,terminal]
120131
----
@@ -123,10 +134,10 @@ $ oc patch mcp/worker --type merge --patch '{"spec":{"paused":false}}'
123134
+
124135
[NOTE]
125136
====
126-
If pools are not unpaused, the cluster is not permitted to update to any future minors and maintenance tasks such as certificate rotation are inhibited. This puts the cluster at risk for future degradation.
137+
If pools are not unpaused, the cluster is not permitted to update to any future minor versions, and maintenance tasks such as certificate rotation are inhibited. This puts the cluster at risk for future degradation.
127138
====
128139

129-
. Verify that your previously paused pools have updated and your cluster completed the update to 4.10, run the following command:
140+
. Verify that your previously paused pools updated and that your cluster completed the update to version 4.10. Run the following command:
130141
+
131142
[source,terminal]
132143
----

0 commit comments

Comments
 (0)