-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18
-
Important
-
None
-
Hypershift Sprint 258, Hypershift Sprint 259
-
2
-
Proposed
-
False
-
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-39371 NodePool Controller doesn't respect LatestSupportedVersion const
- ON_QA
- is cloned by
-
OCPBUGS-39371 NodePool Controller doesn't respect LatestSupportedVersion const
- ON_QA
- links to