Skip to content

Fix release-4.22 configs promoting to wrong release version - #77759

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
jmguzik:fix-release-4.22-configs
Apr 14, 2026
Merged

Fix release-4.22 configs promoting to wrong release version#77759
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
jmguzik:fix-release-4.22-configs

Conversation

@jmguzik

@jmguzik jmguzik commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

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

Summary by CodeRabbit

  • Chores
    • Updated CI operator release configuration for version 4.22 across multiple projects, adjusting promotion targets and release integration identifiers to align with the current release version.

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>
@coderabbitai

coderabbitai Bot commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

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 Plus

Run ID: 32c9cafa-da1b-4f86-b302-17ac9b0f7e7b

📥 Commits

Reviewing files that changed from the base of the PR and between 741e003 and 59443b7.

📒 Files selected for processing (5)
  • ci-operator/config/kubev2v/migration-planner/kubev2v-migration-planner-release-4.22.yaml
  • ci-operator/config/openshift-online/access-transparency-service/openshift-online-access-transparency-service-release-4.22.yaml
  • ci-operator/config/openshift/bpfman-operator/openshift-bpfman-operator-release-4.22.yaml
  • ci-operator/config/openshift/bpfman/openshift-bpfman-release-4.22.yaml
  • ci-operator/config/openstack-lightspeed/operator/openstack-lightspeed-operator-release-4.22.yaml

Walkthrough

Configuration files for multiple CI operator release 4.22 targets were updated by changing promotion targets and release integration names from "5.0" to "4.22", along with corresponding base image references where applicable.

Changes

Cohort / File(s) Summary
OpenShift BPFman Projects
ci-operator/config/openshift/bpfman-operator/openshift-bpfman-operator-release-4.22.yaml, ci-operator/config/openshift/bpfman/openshift-bpfman-release-4.22.yaml
Updated base_images name references, promotion.to, and releases.*.integration.name from "5.0" to "4.22".
Other Release 4.22 Projects
ci-operator/config/kubev2v/migration-planner/kubev2v-migration-planner-release-4.22.yaml, ci-operator/config/openshift-online/access-transparency-service/openshift-online-access-transparency-service-release-4.22.yaml, ci-operator/config/openstack-lightspeed/operator/openstack-lightspeed-operator-release-4.22.yaml
Updated promotion.to and releases.*.integration.name from "5.0" to "4.22", with one file also updating base_images.base.name.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 10
✅ Passed checks (10 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title accurately summarizes the main change: fixing release-4.22 configurations that were promoting to the wrong release version (5.0 instead of 4.22).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed PR modifies only CI operator YAML config files with no Ginkgo test files or test code present.
Test Structure And Quality ✅ Passed PR contains only YAML configuration file changes updating release targets; no Ginkgo test code is present, so test quality criteria are not applicable.
Microshift Test Compatibility ✅ Passed This PR only modifies YAML CI operator configuration files to update release version references from 5.0 to 4.22. No new Ginkgo e2e tests are added, so the check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR modifies YAML configuration files only and does not add any new Ginkgo e2e tests, making this check not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only CI operator configuration YAML files with version string replacements, not deployment manifests, operator code, or controllers.
Ote Binary Stdout Contract ✅ Passed The OTE Binary Stdout Contract check is not applicable to this pull request. The PR exclusively modifies YAML configuration files for CI operator release promotion and base image references. The custom check targets stdout writes in Go code, but this PR contains no Go code, test code, or binary implementations—only static YAML configuration changes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR contains only CI-operator YAML configuration file modifications updating release version references, with no new Ginkgo test code introduced.

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

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

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2026
@openshift-ci
openshift-ci Bot requested review from Akrog and Billy99 April 14, 2026 08:45
@jmguzik

jmguzik commented Apr 14, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 14, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jmguzik: 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-online-access-transparency-service-release-4.22-unit openshift-online/access-transparency-service presubmit Ci-operator config changed
pull-ci-openshift-bpfman-release-4.22-images openshift/bpfman presubmit Ci-operator config changed
pull-ci-openshift-bpfman-release-4.22-security openshift/bpfman presubmit Ci-operator config changed
pull-ci-openshift-bpfman-operator-release-4.22-ci-bundle-operatorbundle openshift/bpfman-operator presubmit Ci-operator config changed
pull-ci-openshift-bpfman-operator-release-4.22-images openshift/bpfman-operator presubmit Ci-operator config changed
pull-ci-openshift-bpfman-operator-release-4.22-security openshift/bpfman-operator presubmit Ci-operator config changed
pull-ci-openshift-bpfman-operator-release-4.22-test-fmt openshift/bpfman-operator presubmit 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.

@danilo-gemoli

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2026
@openshift-ci

openshift-ci Bot commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

[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

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

@danilo-gemoli

Copy link
Copy Markdown
Contributor

/retest-required

@openshift-merge-bot
openshift-merge-bot Bot merged commit adf39ee into openshift:main Apr 14, 2026
14 checks passed
@openshift-ci

openshift-ci Bot commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

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

HarshwardhanPatil07 pushed a commit to HarshwardhanPatil07/release that referenced this pull request Apr 23, 2026
…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>
Prucek pushed a commit to Prucek/release that referenced this pull request Apr 29, 2026
…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>
fjglira pushed a commit to fjglira/release that referenced this pull request Jun 3, 2026
…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>
andrej1991 pushed a commit to andrej1991/release that referenced this pull request Jul 6, 2026
…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>
SachinNinganure pushed a commit to SachinNinganure/release that referenced this pull request Jul 20, 2026
…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>
malingatembo pushed a commit to malingatembo/release that referenced this pull request Aug 5, 2026
…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>
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