Fix release-4.22 configs promoting to wrong release version - #77759
Conversation
Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors. Affected repos: - kubev2v/migration-planner - openshift/bpfman - openshift/bpfman-operator - openshift-online/access-transparency-service - openstack-lightspeed/operator Signed-off-by: Jakub Guzik <jguzik@redhat.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
WalkthroughConfiguration files for multiple CI operator release 4.22 targets were updated by changing promotion targets and release integration names from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 10✅ Passed checks (10 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/pj-rehearse ack |
|
@jmguzik: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danilo-gemoli, jmguzik, Prucek 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 |
|
/retest-required |
|
@jmguzik: 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. |
…t#77759) Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors. Affected repos: - kubev2v/migration-planner - openshift/bpfman - openshift/bpfman-operator - openshift-online/access-transparency-service - openstack-lightspeed/operator Signed-off-by: Jakub Guzik <jguzik@redhat.com>
…t#77759) Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors. Affected repos: - kubev2v/migration-planner - openshift/bpfman - openshift/bpfman-operator - openshift-online/access-transparency-service - openstack-lightspeed/operator Signed-off-by: Jakub Guzik <jguzik@redhat.com>
…t#77759) Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors. Affected repos: - kubev2v/migration-planner - openshift/bpfman - openshift/bpfman-operator - openshift-online/access-transparency-service - openstack-lightspeed/operator Signed-off-by: Jakub Guzik <jguzik@redhat.com>
…t#77759) Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors. Affected repos: - kubev2v/migration-planner - openshift/bpfman - openshift/bpfman-operator - openshift-online/access-transparency-service - openstack-lightspeed/operator Signed-off-by: Jakub Guzik <jguzik@redhat.com>
…t#77759) Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors. Affected repos: - kubev2v/migration-planner - openshift/bpfman - openshift/bpfman-operator - openshift-online/access-transparency-service - openstack-lightspeed/operator Signed-off-by: Jakub Guzik <jguzik@redhat.com>
…t#77759) Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors. Affected repos: - kubev2v/migration-planner - openshift/bpfman - openshift/bpfman-operator - openshift-online/access-transparency-service - openstack-lightspeed/operator Signed-off-by: Jakub Guzik <jguzik@redhat.com>
Five release-4.22 CI configs were incorrectly referencing ocp/5.0 instead of ocp/4.22 in their promotion, releases, and base_images stanzas, causing persistent fast-forward job failures with "invalid branch promoting to current release" errors.
Affected repos:
Summary by CodeRabbit