OPRUN-4705: Remove NewOLMPreflightPermissionChecks FeatureGate - #2957
OPRUN-4705: Remove NewOLMPreflightPermissionChecks FeatureGate#2957pedjak wants to merge 1 commit into
Conversation
The upstream PreflightPermissions feature gate was removed from operator-controller and the downstream mapping was removed from cluster-olm-operator. The gate definition in openshift/api is now dead weight — nothing acts on it. Co-Authored-By: Claude <noreply@anthropic.com>
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
Hello @pedjak! Some important instructions when contributing to openshift/api: |
📝 WalkthroughWalkthroughRemoved the 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@pedjak: This pull request references OPRUN-4705 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. 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. |
PR Summary by QodoRemove NewOLMPreflightPermissionChecks feature gate definition
AI Description
Diagram
High-Level Assessment
Files changed (10)
|
|
/jira refresh |
|
@pedjak: This pull request references OPRUN-4705 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. 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. |
|
/jira refresh |
|
@pedjak: This pull request references OPRUN-4705 which is a valid jira issue. 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. |
|
/lgtm |
|
/test verify-hypershift-integration |
|
PR-Agent: could not find a component named |
|
Scheduling tests matching the |
|
This isn't working? /test verify-hypershift-integration |
|
/override-sticky ci/prow/verify-hypershift-integration This is broken presently until HyperShift bump their deps /lgtm This is walking back a feature that was never promoted and has since been reverted from the product |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-hypershift-integration These overrides will persist across retests on the current HEAD SHA. Pushing a new commit will clear them. Use 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 kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed, tmshort 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 |
|
Both CI failures are unrelated to this change (pure feature gate deletion):
/retest |
|
/retest |
|
/verified by CI This is a removal, and since the CI passed, it means that nothing ought to be trying to use that feature-gate. |
|
@tmshort: 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. |
|
/retest |
|
/override-sticky ci/prow/verify-hypershift-integration |
|
@tmshort: tmshort unauthorized: /override-sticky is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers. 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 kubernetes-sigs/prow repository. |
|
@pedjak: The following test failed, say
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. |
|
@JoelSpeed the sticky override was not sticky when tide tried to merge and wanted to retest... |
Summary
FeatureGateNewOLMPreflightPermissionChecksdefinition fromfeatures/features.gofeatures.mdand allpayload-manifests/featuregates/YAML filesContext
The upstream
PreflightPermissionsfeature gate was removed from operator-controller (operator-framework/operator-controller#767) and the downstream mapping was removed from cluster-olm-operator (cluster-olm-operator#222). The gate definition inopenshift/apiis now dead weight — it is listed as enabled in TechPreview/DevPreview profiles but nothing acts on it.