Skip to content

Fix instaslice-operator CI: operator-sdk 4.20 image does not exist#75244

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
harche:fix-instaslice-operator-sdk-image
Feb 25, 2026
Merged

Fix instaslice-operator CI: operator-sdk 4.20 image does not exist#75244
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
harche:fix-instaslice-operator-sdk-image

Conversation

@harche
Copy link
Contributor

@harche harche commented Feb 24, 2026

Summary

  • Fix broken e2e-bundle-runc pre-merge job for openshift/instaslice-operator by changing operator-sdk base image from 4.20 to 4.19

Problem

PR #73855 changed the instaslice-operator pre-merge CI config to reference operator-sdk name: "4.20" from namespace: origin. This resolves to the image origin_4.20_operator-sdk, which does not exist in the CI image registry (quay.io/openshift/ci or quay-proxy.ci.openshift.org/openshift/ci).

The e2e-bundle-runc job (which is always_run: true) fails at the image import step with:

failed to reimport the tag pipeline:operator-sdk:
  dockerimage.image.openshift.io "quay.io/openshift/ci:origin_4.20_operator-sdk" not found

Instaslice-operator is the only repo in openshift/release using origin_4.20_operator-sdk — all other operators use 4.17 or 4.19 for the operator-sdk image.

Evidence

  • Last passing job: PR #992 (merged Jan 25, before config change)
  • Failing jobs on PR #999 (opened Feb 24, after config change):
  • No PRs were opened on the repo between Feb 6–24, so this went unnoticed

Fix

Change operator-sdk from name: "4.20" to name: "4.19" (which exists and is used by most other operators).

/cc @BhargaviGudi

🤖 Generated with Claude Code

@openshift-ci openshift-ci bot requested a review from BhargaviGudi February 24, 2026 20:45
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 24, 2026
@harche
Copy link
Contributor Author

harche commented Feb 24, 2026

/cc @sairameshv @haircommander

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@harche: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-instaslice-operator-next-4.18-periodics-ci-index-das-operator-bundle openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-4.18-periodics-images openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-4.19-periodics-ci-index-das-operator-bundle openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-4.19-periodics-images openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-ci-index-das-operator-bundle openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-e2e-bundle openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-e2e-bundle-runc openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-images openshift/instaslice-operator presubmit Ci-operator config changed
pull-ci-openshift-instaslice-operator-next-unit openshift/instaslice-operator presubmit Ci-operator config changed
periodic-ci-openshift-instaslice-operator-next-4.19-periodics-e2e-bundle-runc-periodic N/A periodic Ci-operator config changed
periodic-ci-openshift-instaslice-operator-next-4.18-periodics-e2e-bundle-periodic N/A periodic Ci-operator config changed
periodic-ci-openshift-instaslice-operator-next-4.18-periodics-e2e-bundle-runc-periodic N/A periodic Ci-operator config changed
periodic-ci-openshift-instaslice-operator-next-4.19-periodics-e2e-bundle-periodic N/A periodic Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@harche
Copy link
Contributor Author

harche commented Feb 24, 2026

/pj-rehearse pull-ci-openshift-instaslice-operator-next-e2e-bundle-runc

@openshift-ci-robot
Copy link
Contributor

@harche: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@harche
Copy link
Contributor Author

harche commented Feb 24, 2026

/pj-rehearse pull-ci-openshift-instaslice-operator-next-e2e-bundle-runc

@openshift-ci-robot
Copy link
Contributor

@harche: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

@harche: all tests passed!

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.

@harche
Copy link
Contributor Author

harche commented Feb 25, 2026

@harche: all tests passed!

Full PR test history. Your PR dashboard.

Details

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@harche: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 25, 2026
tag: rhel-9-golang-1.23-openshift-4.20
operator-sdk:
name: "4.20"
name: "4.19"
Copy link
Member

Choose a reason for hiding this comment

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

/lgtm
/approve

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

openshift-ci bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche, sairameshv

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

1 similar comment
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche, sairameshv

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

@openshift-merge-bot openshift-merge-bot bot merged commit dc171b6 into openshift:main Feb 25, 2026
14 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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants