-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.13, 4.14, 4.15
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Include supported but not recommended versions is greyout/disabled in Openshift Cluster Update
Version-Release number of selected component (if applicable):
4.14.24
How reproducible:
100%
Steps to Reproduce:
1. Open the web console to upgrade
2. Click on select version
3. click on select new version
4. Include supported but not recommended version is disabled
Actual results:
No versions with 'supported but not recommended'
Expected results:
It should display the versions
Additional info:
When checked from the CLI its same: $ oc adm upgrade --include-not-recommended Cluster version is 4.14.24 Upstream is unset, so the cluster will use an appropriate default. Channel: eus-4.14 (available channels: candidate-4.14, candidate-4.15, eus-4.14, fast-4.14, fast-4.15, stable-4.14, stable-4.15) Recommended updates: VERSION IMAGE 4.14.31 quay.io/openshift-release-dev/ocp-release@sha256:e4424eeec8a386241a5348d556bdd6dd82ea68f4f19f30f71d18963fb5924e9e 4.14.30 quay.io/openshift-release-dev/ocp-release@sha256:2bda857a6a92b9a6cd353e707029218a78ba1b4a60a762d849a2bc0eb4234e25 4.14.29 quay.io/openshift-release-dev/ocp-release@sha256:797ef883017750606771c408de0d3f84ec0f09a1022fb9fb33199c75c54284ed 4.14.28 quay.io/openshift-release-dev/ocp-release@sha256:c5bcd0298deee99caaf3ec88de246f3af84f80225202df46527b6f2b4d0eb3c3 4.14.27 quay.io/openshift-release-dev/ocp-release@sha256:4d30b359aa6600a89ed49ce6a9a5fdab54092bcb821a25480fdfbc47e66af9ec 4.14.26 quay.io/openshift-release-dev/ocp-release@sha256:4fe7d4ccf4d967a309f83118f1a380a656a733d7fcee1dbaf4d51752a6372890 4.14.25 quay.io/openshift-release-dev/ocp-release@sha256:a0ef946ef8ae75aef726af1d9bbaad278559ad8cab2c1ed1088928a0087990b6 No updates which are not recommended based on your cluster configuration are available.
This is an expected behaviour because there aren't any upgradable versions that are having known issues, if there would have been any they would have been displayed.
Since the behaviour isn't discussed on the documentation, hence raising a doc bug to address this behaviour
