Skip to content

OCPBUGS-77281: Add exception for GCE CSI driver images#30870

Open
jsafrane wants to merge 1 commit intoopenshift:mainfrom
jsafrane:gce-pd-exception
Open

OCPBUGS-77281: Add exception for GCE CSI driver images#30870
jsafrane wants to merge 1 commit intoopenshift:mainfrom
jsafrane:gce-pd-exception

Conversation

@jsafrane
Copy link
Contributor

@jsafrane jsafrane commented Mar 12, 2026

GCE does not support ppc64le nor s390x, so they don't publish driver images for these platforms.
We get this image transitively via Kubernetes that runs the driver to test GCE integrations. We don't run these e2e tests in OCP.

Just document the exception. see openshift/release#76171 for the effective exception.

Summary by CodeRabbit

  • Documentation
    • Documented architecture-specific container image availability limitations, noting that certain images are unavailable on specific processor architectures due to upstream support constraints.

The image does not have ppc64le nor s390x version, because those are not
supported on GCE.
@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 12, 2026
@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-77281, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

GCE does not support ppc64le nor s390x, so they don't publish driver images for these platforms.
We get this image transitively via Kubernetes that runs the driver to test GCE integrations. We don't run these e2e tests in OCP.

Just document the exception. see openshift/release#76171 for the effective exception.

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 bertinatto and tkashem March 12, 2026 14:17
@openshift-ci openshift-ci bot added the e2e-images-update Related to images used by e2e tests label Mar 12, 2026
@jsafrane
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 12, 2026
@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-77281, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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.

@coderabbitai
Copy link

coderabbitai bot commented Mar 12, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 15a9c164-a422-4056-9dc7-2c34c2d26eb8

📥 Commits

Reviewing files that changed from the base of the PR and between 0097787 and 8f667c3.

📒 Files selected for processing (1)
  • test/extended/util/image/README.md

Walkthrough

This change adds a new permanent exception for the GCP CSI driver image to the multi-architecture manifest verification list, documenting that upstream GCE PD CSI driver images lack support for ppc64le and s390x architectures.

Changes

Cohort / File(s) Summary
Documentation and Configuration
test/extended/util/image/README.md
Added permanent exception for registry-k8s-io-cloud-provider-gcp-gcp-compute-persistent-disk-csi-driver with note about GCE architecture limitations on ppc64le and s390x.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly references the main change: adding an exception for GCE CSI driver images. It is specific, concise, and accurately summarizes the primary modification to the README file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed This PR modifies only a README file to add documentation about image exceptions. No Ginkgo test definitions or test titles are added or modified.
Test Structure And Quality ✅ Passed PR adds utility files and documentation without test code structures, so custom check requirements are not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan for PR comments
  • Generate coding plan

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

@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-77281, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

Details

In response to this:

GCE does not support ppc64le nor s390x, so they don't publish driver images for these platforms.
We get this image transitively via Kubernetes that runs the driver to test GCE integrations. We don't run these e2e tests in OCP.

Just document the exception. see openshift/release#76171 for the effective exception.

Summary by CodeRabbit

  • Documentation
  • Documented architecture-specific container image availability limitations, noting that certain images are unavailable on specific processor architectures due to upstream support constraints.

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-robot
Copy link

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

Copy link
Member

@smg247 smg247 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 12, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 12, 2026

@jsafrane: 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-fips 8f667c3 link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-microshift 8f667c3 link true /test e2e-aws-ovn-microshift

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.

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

Labels

e2e-images-update Related to images used by e2e tests 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants