From b5ca2684a0d17ba77fdca437e5962f9e1847364a Mon Sep 17 00:00:00 2001
From: Jaromir Hradilek <jhradilek@redhat.com>
Date: Thu, 6 Feb 2025 21:29:53 +0100
Subject: [PATCH] CNV-42747: Added a note about OCP 4.16

This is an edited version of Oren's original content from PR #86933 and
extended by me based on information kindly provided by him.
---
 ...virt-about-control-plane-only-updates.adoc |  2 ++
 ...ates-during-control-plane-only-update.adoc | 20 +++++++++++++++++++
 2 files changed, 22 insertions(+)

diff --git a/modules/virt-about-control-plane-only-updates.adoc b/modules/virt-about-control-plane-only-updates.adoc
index 62f423a6902b..3c8347805b00 100644
--- a/modules/virt-about-control-plane-only-updates.adoc
+++ b/modules/virt-about-control-plane-only-updates.adoc
@@ -12,6 +12,8 @@ After you update from the source EUS version to the next odd-numbered minor vers
 
 When the {product-title} update succeeds, the corresponding update for {VirtProductName} becomes available. You can now update {VirtProductName} to the target EUS version.
 
+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].
+
 [id="preparing-to-update_{context}"]
 == Preparing to update
 
diff --git a/modules/virt-preventing-workload-updates-during-control-plane-only-update.adoc b/modules/virt-preventing-workload-updates-during-control-plane-only-update.adoc
index 63ff7b5d1189..ec9ccfaa02ad 100644
--- a/modules/virt-preventing-workload-updates-during-control-plane-only-update.adoc
+++ b/modules/virt-preventing-workload-updates-during-control-plane-only-update.adoc
@@ -8,6 +8,26 @@
 
 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.
 
+[IMPORTANT]
+====
+{product-title} 4.16 upgraded the underlying {op-system-first} system to version 9.4. To operate correctly, all `virt-launcher` pods in the cluster need to use the same version of {op-system}.
+
+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:
+
+[source,terminal]
+----
+$ oc get kv kubevirt-kubevirt-hyperconverged -o json -n openshift-cnv | jq .status.outdatedVirtualMachineInstanceWorkloads
+0
+----
+
+If the previous command returns a value larger than 0, list all VMIs with outdated `virt-launcher` pods and live migrate them to a new version manually:
+
+[source,terminal]
+----
+$ oc get vmi -l kubevirt.io/outdatedLauncherImage --all-namespaces
+----
+====
+
 .Prerequisites
 
 * 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.