-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.18
-
None
-
Important
-
None
-
Hypershift Sprint 258, Hypershift Sprint 259
-
2
-
Proposed
-
False
-
-
N/A
-
Release Note Not Required
-
Done
This is a clone of issue OCPBUGS-38936. The following is the description of the original issue:
—
Description of problem:
NodePool Controller doesn't respect LatestSupportedVersion https://github.com/openshift/hypershift/blob/main/support/supportedversion/version.go#L19
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create HostedCluster / NodePool 2. Upgrade both HostedCluster and NodePool at the same time to a version higher than the LatestSupportedVersion
Actual results:
NodePool tries to upgrade to the new version while the HostedCluster ValidReleaseImage condition fails with: 'the latest version supported is: "x.y.z". Attempting to use: "x.y.z"'
Expected results:
NodePool ValidReleaseImage condition also fails
Additional info:
- blocks
-
OCPBUGS-39372 NodePool Controller doesn't respect LatestSupportedVersion const
- New
- clones
-
OCPBUGS-38936 NodePool Controller doesn't respect LatestSupportedVersion const
- ON_QA
- is blocked by
-
OCPBUGS-38936 NodePool Controller doesn't respect LatestSupportedVersion const
- ON_QA
- is cloned by
-
OCPBUGS-39372 NodePool Controller doesn't respect LatestSupportedVersion const
- New
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update