[enterprise-4.8] Issue in file updating/preparing-eus-eus-upgrade.adoc

I asked on openshift-sme: when I perform the intermediate update of my control plane from 4.x (EUS) to the 4.x+1 (non-EUS), will the "oc adm upgrade --to-latest" ignore a "latest" 4.x+1.z release that has no upgrade path to 4.x+2 (next EUS)? Is the eus channel designed to ensure that?

The answer was that no one was sure and I got recommendations to specify a fixed 4.x+1.z (for example 4.9.) that has an update path to the next EUS instead of "latest". So the same recommendation should be in product docs, unless someone answers athoritativelly that the EUS channel will never offer an intermediate control plane non-EUS release that cannot move to the next EUS.

Which section(s) is the issue in?

"EUS-to-EUS update" > "Procedure"

What needs fixing?

Is step 5 "oc adm upgrade --to-latest" guaranteed to leave the control plane in a 4.9.z release with an update path to any 4.10.z? Isn't there any risk of ending up with a control plane that cannot be updated to the next EUS in step 8?

Read preparing-eus-eus-upgrade.adoc, focusing on the “EUS-to-EUS update” procedure and step 5. Resolve whether oc adm upgrade --to-latest guarantees a 4.9.z release with a path to 4.10.z, using an authoritative answer rather than the existing uncertainty. Done means the procedure clearly documents the safe recommendation for reaching the next EUS.