Skip to content

[DO NOT MERGE] CVE-2025-47913: test Buildah patch using openshift/crypto fork#501

Open
kunalmemane wants to merge 2 commits intoopenshift:release-4.16from
kunalmemane:CVE-2025-47913-test-buildah-patch
Open

[DO NOT MERGE] CVE-2025-47913: test Buildah patch using openshift/crypto fork#501
kunalmemane wants to merge 2 commits intoopenshift:release-4.16from
kunalmemane:CVE-2025-47913-test-buildah-patch

Conversation

@kunalmemane
Copy link
Contributor

Testing buildah patch with crypto fork.

@openshift-ci-robot
Copy link
Contributor

@kunalmemane: No Jira issue with key CVE-2025 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Testing buildah patch with crypto fork.

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.

@kunalmemane
Copy link
Contributor Author

/hold

@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 Feb 25, 2026
@openshift-ci openshift-ci bot requested review from Moebasim and prabhapa February 25, 2026 13:57
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kunalmemane
Once this PR has been reviewed and has the lgtm label, please assign moebasim for approval. For more information see the Code Review Process.

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

Details 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

@kunalmemane kunalmemane force-pushed the CVE-2025-47913-test-buildah-patch branch from c8d3b9b to e4489cc Compare February 26, 2026 15:11
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 26, 2026

@kunalmemane: 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-ovn-image-ecosystem e4489cc link true /test e2e-aws-ovn-image-ecosystem
ci/prow/security e4489cc link false /test security

Full PR test history. Your PR dashboard.

Details

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.

@prabhapa
Copy link
Contributor

/retest e2e-aws-ovn-image-ecosystem

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 2026

@prabhapa: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test e2e-aws-ovn
/test e2e-aws-ovn-builds
/test e2e-aws-ovn-image-ecosystem
/test images
/test unit
/test verify

The following commands are available to trigger optional jobs:

/test e2e-aws-ovn-builds-techpreview
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-proxy
/test security

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-builder-release-4.16-e2e-aws-ovn
pull-ci-openshift-builder-release-4.16-e2e-aws-ovn-builds
pull-ci-openshift-builder-release-4.16-e2e-aws-ovn-image-ecosystem
pull-ci-openshift-builder-release-4.16-images
pull-ci-openshift-builder-release-4.16-security
pull-ci-openshift-builder-release-4.16-unit
pull-ci-openshift-builder-release-4.16-verify
Details

In response to this:

/retest e2e-aws-ovn-image-ecosystem

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants