Skip to content

Commit 155b4c4

Browse files
adellapeadellape
authored
Merge pull request #56680 from obrown1205/eus2eus_webconsole
2 parents 8a3b460 + 4fda78b commit 155b4c4

File tree

4 files changed

+220
-138
lines changed

4 files changed

+220
-138
lines changed

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

Lines changed: 145 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * updating/preparing-eus-eus-upgrade.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="updating-eus-to-eus-upgrade-cli_{context}"]
7+
= EUS-to-EUS update using the CLI
8+
9+
.Prerequisites
10+
11+
* Verify that machine config pools are unpaused.
12+
* Update the OpenShift CLI (`oc`) to the target version before each update.
13+
14+
[IMPORTANT]
15+
====
16+
It is highly discouraged to skip this prerequisite. If the OpenShift CLI (`oc`) is not updated to the target version before your update, unexpected issues may occur.
17+
====
18+
19+
.Procedure
20+
21+
. Using the Administrator perspective on the web console, update any Operator Lifecycle Manager (OLM) Operators to the versions that are compatible with the version you are updating to. You can find more information on how to perform this action in "Updating installed Operators"; see "Additional resources".
22+
23+
. Verify that all machine config pools display a status of `UPDATED` and that no machine config pool displays a status of `UPDATING`.
24+
To view the status of all machine config pools, run the following command:
25+
+
26+
[source,terminal]
27+
----
28+
$ oc get mcp
29+
----
30+
+
31+
.Example output
32+
+
33+
[source,terminal]
34+
----
35+
NAME CONFIG UPDATED UPDATING
36+
master rendered-master-ecbb9582781c1091e1c9f19d50cf836c True False
37+
worker rendered-worker-00a3f0c68ae94e747193156b491553d5 True False
38+
----
39+
40+
. Change to the `eus-4.12` channel by running the following command:
41+
+
42+
[source,terminal]
43+
----
44+
$ oc adm upgrade channel eus-4.12
45+
----
46+
+
47+
[NOTE]
48+
====
49+
50+
If you receive an error message indicating that `eus-4.12` is not one of the
51+
available channels, this indicates that Red Hat is still rolling out 4.10 to 4.12 EUS updates.
52+
This rollout process generally takes 45-90 days starting at the GA date.
53+
====
54+
+
55+
56+
. Pause all worker machine pools except for the master pool by running the following command:
57+
+
58+
[source,terminal]
59+
----
60+
$ oc patch mcp/worker --type merge --patch '{"spec":{"paused":true}}'
61+
----
62+
+
63+
[NOTE]
64+
====
65+
You cannot pause the master pool.
66+
====
67+
68+
. Update to the latest version by running the following command:
69+
+
70+
[source,terminal]
71+
----
72+
$ oc adm upgrade --to-latest
73+
----
74+
+
75+
.Example output
76+
+
77+
[source,terminal]
78+
----
79+
Updating to latest version 4.11.18
80+
----
81+
82+
. Review the cluster version to ensure that the updates are complete by running the following command:
83+
+
84+
[source,terminal]
85+
----
86+
$ oc adm upgrade
87+
----
88+
+
89+
.Example output
90+
+
91+
[source,terminal]
92+
----
93+
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
94+
version 4.11.18 True False 6m29s Cluster version is 4.11.18
95+
----
96+
97+
. Update to version 4.12 by running the following command:
98+
+
99+
[source,terminal]
100+
----
101+
$ oc adm upgrade --to-latest
102+
----
103+
104+
. Retrieve the cluster version to ensure that the 4.12 updates are complete by running the following command:
105+
+
106+
[source,terminal]
107+
----
108+
$ oc adm upgrade
109+
----
110+
+
111+
.Example output
112+
+
113+
[source,terminal]
114+
----
115+
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
116+
version 4.12.1 True False 6m29s Cluster version is 4.12.1
117+
----
118+
119+
. To update your worker nodes to 4.12, unpause all previously paused machine config pools by running the following command:
120+
+
121+
[source,terminal]
122+
----
123+
$ oc patch mcp/worker --type merge --patch '{"spec":{"paused":false}}'
124+
----
125+
+
126+
[IMPORTANT]
127+
====
128+
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.
129+
====
130+
131+
. Verify that your previously paused pools are updated and that the update to version 4.12 is complete by running the following command:
132+
+
133+
[source,terminal]
134+
----
135+
$ oc get mcp
136+
----
137+
+
138+
.Example output
139+
+
140+
[source,terminal]
141+
----
142+
NAME CONFIG UPDATED UPDATING
143+
master rendered-master-52da4d2760807cb2b96a3402179a9a4c True False
144+
worker rendered-worker-4756f60eccae96fb9dcb4c392c69d497 True False
145+
----

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

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * updating/preparing-eus-eus-upgrade.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="updating-eus-to-eus-upgrade-console_{context}"]
7+
= EUS-to-EUS update using the web console
8+
9+
.Prerequisites
10+
11+
* Verify that machine config pools are unpaused.
12+
* Have access to the web console as a user with `admin` privileges.
13+
14+
.Procedure
15+
16+
. Update any Operator Lifecycle Manager (OLM) Operators to versions that are compatible with both versions you are updating to. You can find more information on how to perform this action in "Preparing for an Operator update"; see "Additional resources".
17+
18+
. Verify that all machine config pools display a status of `Up to date` and that no machine config pool displays a status of `UPDATING`.
19+
+
20+
To view the status of all machine config pools, click *Compute* -> *MachineConfigPools* and review the contents of the *Update status* column.
21+
+
22+
[NOTE]
23+
====
24+
If your machine config pools have an `Updating` status, please wait for this status to change to `Up to date`. This process could take several minutes.
25+
====
26+
27+
. Set your channel to `eus-4.12`.
28+
+
29+
To set your channel, click *Administration* -> *Cluster Settings* -> *Channel*. You can edit your channel by clicking on the current hyperlinked channel.
30+
31+
. Pause all worker machine pools except for the master pool. You can perform this action on the *MachineConfigPools* tab under the *Compute* page. Select the vertical ellipses next to the machine config pool you'd like to pause and click *Pause updates*.
32+
33+
. Update to version 4.11 and complete up to the *Save* step. You can find more information on how to perform these actions in "Updating a cluster by using the web console"; see "Additional resources".
34+
35+
. Ensure that the 4.11 updates are complete by viewing the *Last completed version* of your cluster. You can find this information on the *Cluster Settings* page under the *Details* tab.
36+
37+
. If necessary, update your OLM Operators by using the Administrator perspective on the web console. You can find more information on how to perform these actions in "Updating installed Operators"; see "Additional resources".
38+
39+
. Update to version 4.12 and complete up to the *Save* step. You can find more information on how to perform these actions in "Updating a cluster by using the web console"; see "Additional resources".
40+
41+
. Ensure that the 4.12 update is complete by viewing the *Last completed version* of your cluster. You can find this information on the *Cluster Settings* page under the *Details* tab.
42+
43+
. Unpause all previously paused machine config pools. You can perform this action on the *MachineConfigPools* tab under the *Compute* page. Select the vertical ellipses next to the machine config pool you'd like to unpause and click *Unpause updates*.
44+
+
45+
[IMPORTANT]
46+
====
47+
If pools are not unpaused, the cluster is not permitted to upgrade to any future minor versions, and maintenance tasks such as certificate rotation are inhibited. This puts the cluster at risk for future degradation.
48+
====
49+
50+
. Verify that your previously paused pools are updated and that your cluster has completed the update to version 4.12.
51+
+
52+
You can verify that your pools have updated on the *MachineConfigPools* tab under the *Compute* page by confirming that the *Update status* has a value of *Up to date*.
53+
+
54+
You can verify that your cluster has completed the update by viewing the *Last completed version* of your cluster. You can find this information on the *Cluster Settings* page under the *Details* tab.

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

Lines changed: 2 additions & 138 deletions
Original file line numberDiff line numberDiff line change
@@ -6,148 +6,12 @@
66
[id="updating-eus-to-eus-upgrade_{context}"]
77
= EUS-to-EUS update
88

9-
The following procedure pauses all non-master MachineConfigPools and performs updates from {product-title} 4.10 to 4.11 to 4.12, then unpauses the previously paused MachineConfigPools.
9+
The following procedure pauses all non-master machine config pools and performs updates from {product-title} 4.10 to 4.11 to 4.12, then unpauses the previously paused machine config pools.
1010
Following this procedure reduces the total update duration and the number of times worker nodes are restarted.
1111

1212
.Prerequisites
1313

1414
* Review the release notes for {product-title} 4.11 and 4.12
15-
* Review the release notes and product lifecycles for any layered products and OLM Operators. Some may require updates either before or during an EUS-to-EUS update.
15+
* Review the release notes and product lifecycles for any layered products and Operator Lifecycle Manager (OLM) Operators. Some may require updates either before or during an EUS-to-EUS update.
1616
* Ensure that you are familiar with version-specific prerequisites, such as link:https://docs.openshift.com/container-platform/4.12/updating/updating-cluster-prepare.html#update-preparing-migrate_updating-cluster-prepare[administrator acknowledgement] that is required prior to updating from {product-title} 4.11 to 4.12.
17-
* Verify that MachineConfigPools is unpaused.
18-
* Update OpenShift CLI `oc` to the target version before each update.
1917
20-
.Procedure
21-
22-
. Upgrade any OLM Operators to versions that are compatible with both versions you are updating to.
23-
24-
. Verify that all machine config pools display a status of `UPDATED` and that no machine config pool displays a status of `UPDATING`.
25-
To view the status of all machine config pools, run the following command:
26-
+
27-
[source,terminal]
28-
----
29-
$ oc get mcp
30-
----
31-
+
32-
.Example output
33-
+
34-
Output is trimmed for clarity:
35-
+
36-
[source,terminal]
37-
----
38-
NAME CONFIG UPDATED UPDATING
39-
master rendered-master-ecbb9582781c1091e1c9f19d50cf836c True False
40-
worker rendered-worker-00a3f0c68ae94e747193156b491553d5 True False
41-
----
42-
43-
. Change to the `eus-4.12` channel. Run the following command:
44-
+
45-
[source,terminal]
46-
----
47-
$ oc adm upgrade channel eus-4.12
48-
----
49-
+
50-
[NOTE]
51-
====
52-
The `oc adm upgrade channel` command is only present in 4.9 or later.
53-
54-
If you receive an error message indicating that `eus-4.12` is not one of the
55-
available channels, this indicates that Red Hat is still rolling out 4.10 to 4.12 EUS upgrades.
56-
This rollout process generally takes 45-90 days starting at the GA date.
57-
====
58-
+
59-
60-
. Pause the machine config pools that you want to skip reboots on. Run the following commands:
61-
+
62-
[NOTE]
63-
====
64-
You cannot pause the master pool.
65-
====
66-
+
67-
[source,terminal]
68-
----
69-
$ oc patch mcp/worker --type merge --patch '{"spec":{"paused":true}}'
70-
----
71-
72-
. Update to version 4.11. Run the following command:
73-
+
74-
[source,terminal]
75-
----
76-
$ oc adm upgrade --to-latest
77-
----
78-
+
79-
.Example output
80-
+
81-
[source,terminal]
82-
----
83-
Updating to latest version 4.11.18
84-
----
85-
86-
. Ensure that the 4.11 updates completed by reviewing the cluster version. Run the following command:
87-
+
88-
[source,terminal]
89-
----
90-
$ oc get clusterversion
91-
----
92-
+
93-
.Example output
94-
+
95-
[source,terminal]
96-
----
97-
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
98-
version 4.11.18 True False 6m29s Cluster version is 4.11.18
99-
----
100-
101-
. If necessary, upgrade OLM Operators by using the Administrator perspective on the web console.
102-
103-
. Update to version 4.12. Run the following command:
104-
+
105-
[source,terminal]
106-
----
107-
$ oc adm upgrade --to-latest
108-
----
109-
110-
. Ensure that the 4.12 update completed by retrieving the cluster version. Run the following command:
111-
+
112-
[source,terminal]
113-
----
114-
$ oc get clusterversion
115-
----
116-
+
117-
.Example output
118-
+
119-
[source,terminal]
120-
----
121-
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
122-
version 4.12.1 True False 6m29s Cluster version is 4.12.1
123-
----
124-
125-
. Unpause all previously paused machine config pools. Run the following command:
126-
+
127-
[source,terminal]
128-
----
129-
$ oc patch mcp/worker --type merge --patch '{"spec":{"paused":false}}'
130-
----
131-
+
132-
[NOTE]
133-
====
134-
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.
135-
====
136-
137-
. Verify that your previously paused pools updated and that your cluster completed the update to version 4.12. Run the following command:
138-
+
139-
[source,terminal]
140-
----
141-
$ oc get mcp
142-
----
143-
+
144-
.Example output
145-
+
146-
Output is trimmed for clarity:
147-
+
148-
[source,terminal]
149-
----
150-
NAME CONFIG UPDATED UPDATING
151-
master rendered-master-52da4d2760807cb2b96a3402179a9a4c True False
152-
worker rendered-worker-4756f60eccae96fb9dcb4c392c69d497 True False
153-
----

‎updating/preparing-eus-eus-upgrade.adoc

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,3 +24,22 @@ Verify that no RHEL7 workers are present in the 4.10 cluster before performing a
2424
* All the clusters might update using EUS channels for a conventional update without pools paused, but only clusters with non control-plane `MachineConfigPools` objects can do EUS-to-EUS update with pools paused.
2525
2626
include::modules/updating-eus-to-eus-upgrade.adoc[leveloffset=+1]
27+
28+
include::modules/updating-eus-to-eus-upgrade-console.adoc[leveloffset=+2]
29+
30+
[role="_additional-resources"]
31+
[id="additional-resources_updating-eus-to-eus-upgrade-console"]
32+
.Additional resources
33+
34+
* xref:../operators/admin/olm-upgrading-operators.adoc#olm-changing-update-channel_olm-upgrading-operators[Preparing for an Operator update]
35+
* xref:../updating/updating-cluster-within-minor.adoc#update-upgrading-web_updating-cluster-within-minor[Updating a cluster by using the web console]
36+
* xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Updating installed Operators]
37+
38+
39+
include::modules/updating-eus-to-eus-upgrade-cli.adoc[leveloffset=+2]
40+
41+
[role="_additional-resources"]
42+
[id="additional-resources_updating-eus-to-eus-upgrade-cli"]
43+
.Additional resources
44+
45+
* xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Updating installed Operators]

0 commit comments

Comments
 (0)