Skip to content

[testing] arc testing bump grpc now - #541

Open
sunku5494 wants to merge 1 commit into
openshift:release-4.12from
sunku5494:grpc-4.12
Open

[testing] arc testing bump grpc now#541
sunku5494 wants to merge 1 commit into
openshift:release-4.12from
sunku5494:grpc-4.12

Conversation

@sunku5494

Copy link
Copy Markdown

No description provided.

Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@sunku5494

Copy link
Copy Markdown
Author

/hold

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 4b77a13e-234d-40dd-bfec-86764e73a3e6

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

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

@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 Jul 20, 2026
@openshift-ci
openshift-ci Bot requested review from moebasim and sayan-biswas July 20, 2026 18:34
@openshift-ci

openshift-ci Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sunku5494
Once this PR has been reviewed and has the lgtm label, please assign prabhapa 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

@sunku5494 sunku5494 changed the title [testing] arc testing bump grpc [testing] arc testing bump grpc now Jul 31, 2026
@sunku5494

Copy link
Copy Markdown
Author

CI for this PR has finished and the following jobs failed:

  • e2e-aws-ovn-builds

ARC is assessing these CI job failures through AI skill assistance. Based on that assessment:

  • Auto-retesting will take place for jobs whose failure is classified as an infrastructure flake
  • ARC will post a follow-up comment with each CI job's failure analysis

@sunku5494

Copy link
Copy Markdown
Author

CI Failure Analysis

ARC assessed the following failed CI jobs via AI skill assistance:

e2e-aws-ovn-builds

  • Category: Infrastructure Flake ---
  • Summary: The openshift-e2e-test step failed because the [sig-builds] test could not pull the centos:latest base image from any registry — CentOS is EOL'd and the image no longer exists anywhere. The cluster provisioned successfully; the builder PR code was never actually exercised. ---
  • Failed step: - **Step name:** openshift-e2e-test- **Phase:**test- **Step script:**ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh ---

Retesting infrastructure flake jobs:
/test e2e-aws-ovn-builds

Note: Required status of Prow CI jobs was determined based on this repository and branch's Prow configuration and GitHub branch protection settings as of 2026-07-31, when this PR was first detected. Only required CI failures are assessed.

@openshift-ci

openshift-ci Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

@sunku5494: 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/security 6b8b05f link false /test security
ci/prow/e2e-aws-ovn-builds 6b8b05f link true /test e2e-aws-ovn-builds

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.

@sunku5494

Copy link
Copy Markdown
Author

CI for this PR has finished and the following jobs failed:

  • e2e-aws-ovn-builds

ARC is assessing these CI job failures through AI skill assistance (this is re-assessment attempt 2, after previous retest). Based on that assessment:

  • Auto-retesting will take place for jobs whose failure is classified as an infrastructure flake
  • ARC will post a follow-up comment with each CI job's failure analysis

@sunku5494

Copy link
Copy Markdown
Author

CI Failure Analysis

ARC assessed the following failed CI jobs via AI skill assistance:

e2e-aws-ovn-builds

  • Category: Code Issue (test fixture uses an EOL base image — unrelated to this PR) ---
  • Summary: The e2e test failed because the test fixture Dockerfile uses FROM centos (CentOS Linux EOL), and centos:latest is no longer available from any registry. This failure is unrelated to the PR changes (a gRPC vendor dependency bump). ---
  • Failed step: - **Step name:** openshift-e2e-test- **Phase:** test - **Step script:**ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh- **Pod:**e2e-aws-ovn-builds-openshift-e2e-test(namespaceci-op-x4g8gry8) - **Duration:** 50m37s before failure (exit code 1) ---

The following CI job(s) failed due to issues in this PR's changes, not CI infrastructure:

  • e2e-aws-ovn-builds

Please investigate and fix the above failures.

cc @sunku5494 — please take a look.

Note: Required status of Prow CI jobs was determined based on this repository branch's Prow configuration and GitHub branch protection settings as of 2026-07-31, when this PR was first detected. Only required CI failures are assessed.

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.

1 participant