OCPBUGS-120840: remove TechPreviewNoUpgrade from AWS cluster creation args - #9535
Conversation
…on args The control-plane-upgrade test was failing because it attempted to upgrade a cluster with TechPreviewNoUpgrade enabled. This exposed a pre-existing OCP bug in the CSI snapshot controller CRDs: v1beta2 was removed from spec.versions but still present in status.storedVersions, violating Kubernetes storage-version migration rules. TechPreviewNoUpgrade clusters should not be upgraded — upgrading a TechPreview cluster to a release that has graduated those APIs (removing the preview versions) is out of scope for the control-plane-upgrade test. Removing TechPreviewNoUpgrade from the default CreateArgs ensures the test cluster uses stable API versions that don't change between 4.22 and 5.0, allowing the upgrade to proceed without CRD conflicts. Fixes OCPBUGS-120840.
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughAWS cluster creation no longer passes Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to AWS test cluster creation now enables TechPreviewNoUpgrade only for public and Karpenter variants, allowing upgrade variants to use stable APIs. No current merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@vismishr: This pull request references Jira Issue OCPBUGS-120840, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9535 +/- ##
==========================================
+ Coverage 47.21% 47.38% +0.17%
==========================================
Files 791 793 +2
Lines 99517 99813 +296
==========================================
+ Hits 46989 47301 +312
+ Misses 49366 49349 -17
- Partials 3162 3163 +1 see 24 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
/jira refresh |
|
@celebdor: This pull request references Jira Issue OCPBUGS-120840, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/approve |
|
/verified by E2E passing |
|
@jparrill: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
This removes it from all hosted clusters being tested, not just upgrade tests. Under what circumstances should the flag be enabled? Because with this PR it's no longer enabled for any tests at all |
|
We should narrow the scope to only the cluster that will be used for an upgrade test and not all clusters |
| // Enables Karpenter-based node provisioning (AutoNode) | ||
| "--auto-node", | ||
| // Required for karpenter to reach the hosted cluster API server from the mgmt cluster | ||
| "--endpoint-access=PublicAndPrivate", |
There was a problem hiding this comment.
"--feature-set=TechPreviewNoUpgrade"
| { | ||
| Variant: "public", | ||
| ExtraArgs: append(extraArgs, []string{ | ||
| "--public-only", |
There was a problem hiding this comment.
"--feature-set=TechPreviewNoUpgrade",
Remove TechPreviewNoUpgrade from global CreateArgs() and add it only to variants that need it (public, karpenter). Keep it off upgrade variants so the control-plane-upgrade test can use stable GA APIs. The control-plane-upgrade test was failing because it attempted to upgrade a cluster with TechPreviewNoUpgrade enabled, which exposed a CSI snapshot controller CRD storage-version conflict: v1beta2 was removed from spec.versions but still present in status.storedVersions. Upgrade tests should use stable APIs, not preview features. TechPreview feature testing is scoped to public and karpenter variants. Fixes OCPBUGS-120840.
|
@vismishr: This pull request references Jira Issue OCPBUGS-120840, which is valid. 3 validation(s) were run on this bug
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Scheduling tests matching the |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: csrwng, jparrill, vismishr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test images |
|
/test okd-scos-images |
1 similar comment
|
/test okd-scos-images |
|
/verified by E2E passing |
|
@jparrill: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Test Resultse2e-aws
e2e-aks
|
|
@vismishr: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@vismishr: Jira Issue Verification Checks: Jira Issue OCPBUGS-120840 Jira Issue OCPBUGS-120840 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Summary
Fixes OCPBUGS-120840: control-plane-upgrade test was failing due to TechPreviewNoUpgrade being applied globally to all test clusters.
Root Cause
--feature-set=TechPreviewNoUpgradewas in the globalCreateArgs(), affecting ALL clusters including upgrade variants. When upgrade tests run on TechPreview clusters, they expose a CSI snapshot controller CRD storage-version conflict: v1beta2 was removed from spec.versions but still present in status.storedVersions.Fix
TechPreviewNoUpgradefrom globalCreateArgs()Upgrade tests should use stable GA APIs, not preview features.
Testing
Fixes: OCPBUGS-120840
Summary by CodeRabbit
TechPreviewNoUpgradefeature set.publicandkarpentervariants now use theTechPreviewNoUpgradefeature set.