Skip to content

NE-2649: Update FBCs v4.12-v4.21 with prod v1.1.2 bundle#434

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
grzpiotrowski:edo-1-1-2-update-prod-fbc
Apr 30, 2026
Merged

NE-2649: Update FBCs v4.12-v4.21 with prod v1.1.2 bundle#434
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
grzpiotrowski:edo-1-1-2-update-prod-fbc

Conversation

@grzpiotrowski
Copy link
Copy Markdown
Contributor

Replace the stage v1.1.2 bundle image with the production one from registry.redhat.io in all FBC catalogs. The bundle digest changed because of the operand pipeline change between the stage and production release. No code changes involved.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 29, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 29, 2026

@grzpiotrowski: This pull request references NE-2649 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Replace the stage v1.1.2 bundle image with the production one from registry.redhat.io in all FBC catalogs. The bundle digest changed because of the operand pipeline change between the stage and production release. No code changes involved.

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
Copy Markdown

coderabbitai Bot commented Apr 29, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 130cb2df-e17c-47ef-ad4a-2d2e657335ad

📥 Commits

Reviewing files that changed from the base of the PR and between 9441df6 and 69e45a9.

📒 Files selected for processing (20)
  • catalog/v4.12/catalog-template.yaml
  • catalog/v4.12/catalog.yaml
  • catalog/v4.13/catalog-template.yaml
  • catalog/v4.13/catalog.yaml
  • catalog/v4.14/catalog-template.yaml
  • catalog/v4.14/catalog.yaml
  • catalog/v4.15/catalog-template.yaml
  • catalog/v4.15/catalog.yaml
  • catalog/v4.16/catalog-template.yaml
  • catalog/v4.16/catalog.yaml
  • catalog/v4.17/catalog-template.yaml
  • catalog/v4.17/catalog.yaml
  • catalog/v4.18/catalog-template.yaml
  • catalog/v4.18/catalog.yaml
  • catalog/v4.19/catalog-template.yaml
  • catalog/v4.19/catalog.yaml
  • catalog/v4.20/catalog-template.yaml
  • catalog/v4.20/catalog.yaml
  • catalog/v4.21/catalog-template.yaml
  • catalog/v4.21/catalog.yaml
✅ Files skipped from review due to trivial changes (7)
  • catalog/v4.20/catalog-template.yaml
  • catalog/v4.15/catalog-template.yaml
  • catalog/v4.14/catalog-template.yaml
  • catalog/v4.19/catalog-template.yaml
  • catalog/v4.13/catalog-template.yaml
  • catalog/v4.21/catalog-template.yaml
  • catalog/v4.18/catalog-template.yaml
🚧 Files skipped from review as they are similar to previous changes (4)
  • catalog/v4.12/catalog-template.yaml
  • catalog/v4.17/catalog-template.yaml
  • catalog/v4.16/catalog-template.yaml
  • catalog/v4.17/catalog.yaml

📝 Walkthrough

Walkthrough

This pull request updates OLM bundle catalog entries for external-dns-operator.v1.1.2 across Kubernetes versions v4.12–v4.21. Image references are migrated from registry.stage.redhat.io to registry.redhat.io, with bundle and related-image SHA256 digests replaced by production equivalents. Both catalog-template.yaml and catalog.yaml files are modified; catalog.yaml updates also include refreshed createdAt timestamps and adjusted relatedImages entries to reflect the new registry references.

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main changeset: updating FBC catalogs v4.12-v4.21 with the production v1.1.2 bundle image, replacing stage registry references.
Description check ✅ Passed The description clearly relates to the changeset, explaining the replacement of stage bundle images with production images across FBC catalogs and noting the digest change and absence of code changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR modifies only YAML catalog files, not Go test files, so Ginkgo test naming check is not applicable.
Test Structure And Quality ✅ Passed This custom check is not applicable to the provided pull request. The PR exclusively modifies YAML catalog manifest files to update external-dns-operator bundle image references, with no changes to test files.
Microshift Test Compatibility ✅ Passed This pull request does not add any new Ginkgo e2e tests or test code files; changes consist entirely of YAML catalog manifest updates.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR modifies only OLM catalog configuration files with no Ginkgo e2e tests added, making the check not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only OLM catalog metadata files with image digest updates. Custom check applies to deployment manifests, operator code, and controllers defining scheduling constraints, none of which are present.
Ote Binary Stdout Contract ✅ Passed The OTE Binary Stdout Contract check is not applicable because this PR contains only YAML catalog data file modifications with no Go code changes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Pull request contains only YAML catalog configuration changes updating OLM bundle image references and digests. No new Ginkgo e2e tests are present in modified files.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.

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

@grzpiotrowski
Copy link
Copy Markdown
Contributor Author

/hold

wait for #424

@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 Apr 29, 2026
@openshift-ci openshift-ci Bot requested review from Thealisyed and gcs278 April 29, 2026 13:14
Replace the stage `v1.1.2` bundle image with the production one
from `registry.redhat.io` in all FBC catalogs. The bundle digest
changed because of the operand pipeline change between the stage and
production release. No code changes involved.
@grzpiotrowski grzpiotrowski force-pushed the edo-1-1-2-update-prod-fbc branch from 9441df6 to 69e45a9 Compare April 29, 2026 14:28
@grzpiotrowski
Copy link
Copy Markdown
Contributor Author

rebased after #424

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 29, 2026
Copy link
Copy Markdown
Contributor

@alebedev87 alebedev87 left a comment

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 Apr 29, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 29, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

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-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 29, 2026
@grzpiotrowski
Copy link
Copy Markdown
Contributor Author

  Created ClusterTemplateInstance cluster-4gdgw
  Waiting for ClusterTemplateInstance to be ready (30m timeout)
  error: timed out waiting for the condition on clustertemplateinstances/cluster-4gdgw

/test "Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14"

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 29, 2026

@grzpiotrowski: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test ci-bundle-external-dns-operator-bundle
/test e2e-aws-operator
/test e2e-aws-shared-vpc-phz-operator
/test e2e-azure-infoblox-operator
/test e2e-azure-operator
/test e2e-gcp-operator
/test images
/test unit
/test verify

Use /test all to run all jobs.

Details

In response to this:

 Created ClusterTemplateInstance cluster-4gdgw
 Waiting for ClusterTemplateInstance to be ready (30m timeout)
 error: timed out waiting for the condition on clustertemplateinstances/cluster-4gdgw

/test "Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14"

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 29, 2026

@grzpiotrowski: 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.

@alebedev87
Copy link
Copy Markdown
Contributor

4.14 deploy operator pipeline tries to install 4.14.64 version which seems like it was withdrawn from the upgrade graphs. This may be a reason for the perma-failure of the installation.

@alebedev87
Copy link
Copy Markdown
Contributor

/override "Red Hat Konflux kflux-prd-rh03 / Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14"

Reason: #434 (comment).

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 30, 2026

@alebedev87: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • Red Hat Konflux kflux-prd-rh03 / Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14

Only the following failed contexts/checkruns were expected:

  • CodeRabbit
  • Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14
  • ci/prow/ci-bundle-external-dns-operator-bundle
  • ci/prow/e2e-aws-operator
  • ci/prow/e2e-aws-shared-vpc-phz-operator
  • ci/prow/e2e-azure-infoblox-operator
  • ci/prow/e2e-azure-operator
  • ci/prow/e2e-gcp-operator
  • ci/prow/images
  • ci/prow/unit
  • ci/prow/verify
  • pull-ci-openshift-external-dns-operator-main-ci-bundle-external-dns-operator-bundle
  • pull-ci-openshift-external-dns-operator-main-e2e-aws-operator
  • pull-ci-openshift-external-dns-operator-main-e2e-aws-shared-vpc-phz-operator
  • pull-ci-openshift-external-dns-operator-main-e2e-azure-infoblox-operator
  • pull-ci-openshift-external-dns-operator-main-e2e-azure-operator
  • pull-ci-openshift-external-dns-operator-main-e2e-gcp-operator
  • pull-ci-openshift-external-dns-operator-main-images
  • pull-ci-openshift-external-dns-operator-main-unit
  • pull-ci-openshift-external-dns-operator-main-verify
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override "Red Hat Konflux kflux-prd-rh03 / Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14"

Reason: #434 (comment).

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.

@alebedev87
Copy link
Copy Markdown
Contributor

/override "Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14"

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 30, 2026

@alebedev87: Overrode contexts on behalf of alebedev87: Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14

Details

In response to this:

/override "Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14"

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.

@openshift-merge-bot openshift-merge-bot Bot merged commit f3b05b5 into openshift:main Apr 30, 2026
33 of 34 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. 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