NE-2649: Update FBCs v4.12-v4.21 with prod v1.1.2 bundle#434
Conversation
|
@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. DetailsIn response to this:
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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (20)
✅ Files skipped from review due to trivial changes (7)
🚧 Files skipped from review as they are similar to previous changes (4)
📝 WalkthroughWalkthroughThis pull request updates OLM bundle catalog entries for 🚥 Pre-merge checks | ✅ 12✅ Passed checks (12 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 60 minutes.Comment |
|
/hold wait for #424 |
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.
9441df6 to
69e45a9
Compare
|
rebased after #424 /unhold |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test "Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14" |
|
@grzpiotrowski: The specified target(s) for Use DetailsIn response to this:
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. |
|
@grzpiotrowski: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
|
|
/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). |
|
@alebedev87: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn response to this:
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. |
|
/override "Red Hat Konflux / ext-dns-optr-fbc-v4-14-deploy-operator / external-dns-fbc-container-ext-dns-optr-fbc-v4-14" |
|
@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 DetailsIn response to this:
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. |
f3b05b5
into
openshift:main
Replace the stage
v1.1.2bundle image with the production one fromregistry.redhat.ioin all FBC catalogs. The bundle digest changed because of the operand pipeline change between the stage and production release. No code changes involved.