Document URL: https://docs.openshift.com/container-platform/4.10/updating/preparing-eus-eus-upgrade.html Section Number and Name: Prerequisites Describe the issue: The oc command version 4.8 and earlier doesn't offer the `oc adm upgrade channel` command, and worse if used it provides no indication that the command failed. Suggestions for improvement: We should detail both in Prerequisites, and on first use, that they need to use oc version 4.9 or later when starting the EUS-to-EUS upgrade. This is particularly prudent right now since they're going to be upgrading from 4.8 to 4.10. Additional information: I'll put in a PR for this.
> Describe the issue: The oc command version 4.8 and earlier doesn't offer the `oc adm upgrade channel` command, and worse if used it provides no indication that the command failed. Hi Scott It seems we already have such Prerequisites described in the doc[1]: ``` Prerequisites Install the OpenShift CLI (oc) that matches the version for your updated version. ``` According to above, the user(for eus upgrade) should update `oc` to v4.9 before updating cluster from v4.8 to v4.9, and then update `oc` to v4.10 before updating cluster from v4.9 to v4.10. The upgrade steps for EUS-to-EUS is also `upgrade with cli`. Do you think we need add this Prerequisites again? [1] https://docs.openshift.com/container-platform/4.8/updating/updating-cluster-cli.html#update-upgrading-cli_updating-cluster-cli
Jia, I think that's a valid point, the EUS-to-EUS upgrade docs however are written as a freestanding procedure so I think we should make reference to the need to use at least a 4.9 CLI in this page and given the nature of EUS-to-EUS upgrade we should probably try to clarify whether that'd be 4.9 or 4.10. I chose 4.9 because it should offer the best compatibility between 4.8, 4.9, and 4.10. I'm sure that using 4.10 would work for at least initiating the upgrade. My biggest concern right now is that the docs as written may lead someone to use 4.8 and there's no error message generated by `oc adm upgrade channel eus-4.10` command when that's the case because it's an unknown command. If they were running 4.9 it would tell them that the channel is not yet available and I want to make sure we get that change made sooner rather than later. Once we're past 4.8 to 4.10 we can revert back to just saying that the CLI should be updated using version generic language.
This change is live in 4.10: https://docs.openshift.com/container-platform/4.10/updating/preparing-eus-eus-upgrade.html#updating-eus-to-eus-upgrade_eus-to-eus-upgrade