QE

Author: ousleyp

modules/virt-preventing-workload-updates-during-eus-update.adoc

@@ -16,6 +16,13 @@ When you update from one Extended Update Support (EUS) version to the next, you
 
 * You paused the worker nodes' machine config pools as directed by the {product-title} documentation.
 
+* Your {VirtProductName} subscription uses the *Automatic* approval strategy.
++
+[NOTE]
+====
+If you use the *Manual* approval strategy, you must approve all pending updates in the web console. This is discouraged because your cluster becomes unsupported if your {VirtProductName} and {product-title} versions are out of sync. For more details, refer to the "Manually approving a pending Operator update" section.
+====
+
 .Procedure
 
 . Back up the current `workloadUpdateMethods` configuration by running the following command:
@@ -117,19 +124,16 @@ $ oc get clusterversion
 Updating {product-title} to the next version is a prerequisite for updating {VirtProductName}. For more details, refer to the "Updating clusters" section of the {product-title} documentation.
 ====
 
-. If you use the recommended *Automatic* approval strategy, which is enabled by default, {VirtProductName} automatically updates to the corresponding version after you update {product-title}. Monitor the {VirtProductName} update by running the following command:
+. With the default *Automatic* approval strategy, {VirtProductName} automatically updates to the corresponding version after you update {product-title}. Monitor the {VirtProductName} update by running the following command:
 +
 [source,terminal]
 ----
 $ oc get csv -n openshift-cnv
 ----
-+
-[NOTE]
-====
-If you used the *Manual* approval strategy, you must approve the update in the web console. For more details, refer to the "Manually approving a pending Operator update" section.
-====
 
-. Confirm that {VirtProductName} successfully updated to the non-EUS version by running the following command:
+. Continue to monitor as {VirtProductName} updates to the z-stream versions that are available for the non-EUS version.
+
+. Confirm that {VirtProductName} successfully updated to the latest z-stream release of the non-EUS version by running the following command:
 +
 [source,terminal]
 ----
@@ -154,10 +158,21 @@ $ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.vers
 $ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.conditions"
 ----
 
-. Continue to update your cluster and {VirtProductName} as described in the preceding steps, monitoring to ensure that the updates succeed.
-.. Update {product-title} and, subsequently, {VirtProductName}, until you install the latest z-stream release of the non-EUS minor version. Ensure that you update both {product-title} and {VirtProductName} to this version.
-.. Update {product-title} to the target EUS version.
-.. Update {VirtProductName} to the target EUS version.
+. Update to the target EUS version.
+.. Update {product-title} to the target EUS version. Confirm that the update succeeded by checking the cluster version:
++
+[source,terminal]
+----
+$ oc get clusterversion
+----
+.. After {product-title} updates, {VirtProductName} automatically updates to the target EUS version. Monitor the update by running the following command:
++
+[source,terminal]
+----
+$ oc get csv -n openshift-cnv
+----
++
+The update completes when the `VERSION` field matches the target EUS version and the `PHASE` field reads `Succeeded`.
 
 . Restore the workload update methods configuration that you backed up:
 +