-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.13, 4.14, 4.15, 4.16, 4.17, 4.18, 4.19, 4.20, 4.21
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem
Current docs have oc adm upgrade output that includes:
No updates available. You may force an update to a specific release image...
But we replaced that "force" language in 4.13:
$ for Y in $(seq 12 21); do git --no-pager grep 'specific release image' "origin/release-4.${Y}" -- pkg/cli/admin/upgrade/upgrade.go; done
origin/release-4.12:pkg/cli/admin/upgrade/upgrade.go: fmt.Fprintf(o.Out, "No updates available. You may force an upgrade to a specific release image, but doing so may not be supported and may result in downtime or data loss.\n")
origin/release-4.13:pkg/cli/admin/upgrade/upgrade.go: fmt.Fprintf(o.Out, "No updates available. You may still upgrade to a specific release image with --to-image or wait for new updates to be available.\n")
...
Version-Release number of selected component
4.13 and later oc have the new language. Doesn't seem like a change that's likely to trip up customers, so while I think we should fix it in the dev branch, I'm agnostic about whether we backport the fix to older docs.
How reproducible
Every time.
Steps to Reproduce
1. Read CLI update docs.
Actual results
Stale "...You may force an update..." example.
Expected results
Current output:
No updates available. You may still upgrade to a specific release image with --to-image or wait for new updates to be available.