Skip to content

Commit 70e240a

Browse files
authored
Merge pull request #88204 from jhradilek/CNV-42747-workload-updates
CNV-42747: Added a note about OCP 4.16
2 parents c3bf98d + ac79e7f commit 70e240a

File tree

2 files changed

+24
-1
lines changed

2 files changed

+24
-1
lines changed

modules/virt-about-control-plane-only-updates.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ After you update from the source EUS version to the next odd-numbered minor vers
1212

1313
When the {product-title} update succeeds, the corresponding update for {VirtProductName} becomes available. You can now update {VirtProductName} to the target EUS version.
1414

15+
For more information about EUS versions, see the link:https://access.redhat.com/support/policy/updates/openshift[Red Hat OpenShift Container Platform Life Cycle Policy].
16+
1517
[id="preparing-to-update_{context}"]
1618
== Preparing to update
1719

modules/virt-preventing-workload-updates-during-control-plane-only-update.adoc

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,27 @@
88

99
When you update from one Extended Update Support (EUS) version to the next, you must manually disable automatic workload updates to prevent {VirtProductName} from migrating or evicting workloads during the update process.
1010

11+
[IMPORTANT]
12+
====
13+
In {product-title} 4.16, the underlying {op-system-first} upgraded to version 9.4 of {op-system-base-full}. To operate correctly, all `virt-launcher` pods in the cluster need to use the same version of {op-system-base}.
14+
15+
After upgrading to {product-title} 4.16 from an earlier version, re-enable workload updates in {VirtProductName} to allow `virt-launcher` pods to update. Before upgrading to the next {product-title} version, verify that all VMIs use up-to-date workloads:
16+
17+
[source,terminal]
18+
----
19+
$ oc get kv kubevirt-kubevirt-hyperconverged -o json -n openshift-cnv | jq .status.outdatedVirtualMachineInstanceWorkloads
20+
----
21+
22+
If the previous command returns a value larger than `0`, list all VMIs with outdated `virt-launcher` pods and start live migration to update them to a new version:
23+
24+
[source,terminal]
25+
----
26+
$ oc get vmi -l kubevirt.io/outdatedLauncherImage --all-namespaces
27+
----
28+
29+
For the list of supported {product-title} releases and the {op-system-base} versions they use, see link:https://access.redhat.com/articles/6907891[{op-system-base} Versions Utilized by {op-system} and {product-title}].
30+
====
31+
1132
.Prerequisites
1233

1334
* You are running an EUS version of {product-title} and want to update to the next EUS version. You have not yet updated to the odd-numbered version in between.
@@ -206,4 +227,4 @@ $ oc get vmim -A
206227
207228
.Next steps
208229

209-
* You can now unpause the worker nodes' machine config pools.
230+
* Unpause the machine config pools for each compute node.

0 commit comments

Comments
 (0)