Skip to content

Conversation

@RishabhSaini
Copy link
Contributor

features: Lift feature gate for PIS

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 10, 2025

Hello @RishabhSaini! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 10, 2025
@RishabhSaini RishabhSaini changed the title Promote PinnedImageSet feature gate to default feature set MCO-1524: Promote PinnedImageSet feature gate to default feature set Apr 10, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 10, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 10, 2025

@RishabhSaini: This pull request references MCO-1524 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 "4.19.0" version, but no target version was set.

In response to this:

features: Lift feature gate for PIS

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.

@openshift-ci openshift-ci bot requested review from cgwalters and deads2k April 10, 2025 13:56
@RishabhSaini
Copy link
Contributor Author

/test verify-feature-promotion

@JoelSpeed
Copy link
Contributor

/retest

@isabella-janssen
Copy link
Member

/hold

This depends on the GA of the MachineConfigNode feature (#2288).

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 21, 2025
@RishabhSaini
Copy link
Contributor Author

/test verify-feature-promotion

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 22, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 19, 2025
@yuqi-zhang
Copy link
Contributor

/hold cancel

#2288 has merged and this can go ahead. Note that much like #2288 (comment) , the test names were changed.

The failures in verify-crd-schema seem to be related to legacy MCP fields since this changes that API. Perhaps we should override that since we don't want to change any legacy fields in this PR?

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 19, 2025
@JoelSpeed
Copy link
Contributor

Reviewing the promotion results, since the tests were renamed, we have the 14 required runs and there have been no failures, showing 100% across the board. Taking into account the renames, the worst pass rate is 94%, but since these results are older than a week, we can discount these failures now

/lgtm
/override ci/prow/verify-feature-promotion
/override ci/prow/verify-crd-schema

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 20, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, RishabhSaini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 20, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 20, 2025

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema, ci/prow/verify-feature-promotion

In response to this:

Reviewing the promotion results, since the tests were renamed, we have the 14 required runs and there have been no failures, showing 100% across the board. Taking into account the renames, the worst pass rate is 94%, but since these results are older than a week, we can discount these failures now

/lgtm
/override ci/prow/verify-feature-promotion
/override ci/prow/verify-crd-schema

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 20, 2025

@RishabhSaini: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-serial a25a302 link true /test e2e-aws-serial
ci/prow/e2e-aws-serial-techpreview a25a302 link true /test e2e-aws-serial-techpreview

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 5df20f3 into openshift:master Jun 20, 2025
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants