Skip to content

[NO-JIRA] Sync Dockerfile.ocp image#1126

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
jhadvig:builder_release-4.21
Mar 17, 2026
Merged

[NO-JIRA] Sync Dockerfile.ocp image#1126
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
jhadvig:builder_release-4.21

Conversation

@jhadvig
Copy link
Copy Markdown
Member

@jhadvig jhadvig commented Mar 17, 2026

No description provided.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 17, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9ab3894f-f1a0-4429-8590-9754b26badcc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.

Add a .trivyignore file to your project to customize which findings Trivy reports.

@jhadvig jhadvig added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. verified Signifies that the PR passed pre-merge verification criteria labels Mar 17, 2026
@jhadvig
Copy link
Copy Markdown
Member Author

jhadvig commented Mar 17, 2026

/label backport-risk-assessed

@jhadvig jhadvig added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 17, 2026
@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 17, 2026
@openshift-ci openshift-ci Bot requested review from TheRealJon and spadgett March 17, 2026 14:07
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig

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

The pull request process is described 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

@jhadvig
Copy link
Copy Markdown
Member Author

jhadvig commented Mar 17, 2026

Overriding since the actual change is done in openshift/release#76399
/override ci/prow/e2e-aws-console ci/prow/e2e-aws-operator ci/prow/e2e-azure-ovn-upgrade ci/prow/e2e-gcp-ovn

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 17, 2026

@jhadvig: Overrode contexts on behalf of jhadvig: ci/prow/e2e-aws-console, ci/prow/e2e-aws-operator, ci/prow/e2e-azure-ovn-upgrade, ci/prow/e2e-gcp-ovn

Details

In response to this:

Overriding since the actual change is done in openshift/release#76399
/override ci/prow/e2e-aws-console ci/prow/e2e-aws-operator ci/prow/e2e-azure-ovn-upgrade ci/prow/e2e-gcp-ovn

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.

@jhadvig jhadvig added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 17, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 898badb into openshift:release-4.21 Mar 17, 2026
11 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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants