Skip to content

Revert "Revert "OSAC-360: Update Go version in osac-project installer config""#79843

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
omer-vishlitzky:revert-79839-revert-79754-patch-9
May 28, 2026
Merged

Revert "Revert "OSAC-360: Update Go version in osac-project installer config""#79843
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
omer-vishlitzky:revert-79839-revert-79754-patch-9

Conversation

@omer-vishlitzky
Copy link
Copy Markdown
Contributor

Reverts #79839

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

openshift-ci-robot commented May 28, 2026

@omer-vishlitzky: This pull request references OSAC-360 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 task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Reverts #79839

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
Contributor

coderabbitai Bot commented May 28, 2026

Walkthrough

The OSAC installer CI configuration is updated to use a newer build root image stream tag. The build environment is upgraded from RHEL 9 with Go 1.25 and OpenShift 4.21 to RHEL 9 with Go 1.26 and OpenShift 5.0.

Changes

OSAC Installer Build Root Image Configuration

Layer / File(s) Summary
Build root image stream tag update
ci-operator/config/osac-project/osac-installer/osac-project-osac-installer-main.yaml
The build_root.image_stream_tag.tag value is updated from rhel-9-release-golang-1.25-openshift-4.21 to rhel-9-release-golang-1.26-openshift-5.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • openshift/release#79754: Updates the same file with the same Go 1.25/OpenShift 4.21 to Go 1.26/OpenShift 5.0 builder variant transition.
  • openshift/release#79717: Modifies OpenShift image stream tags with the same Go 1.25/OpenShift 4.21 to Go 1.26/OpenShift 5.0 variant update pattern.
  • openshift/release#79839: Modifies the same line in this configuration file, reverting a prior update to the build_root image stream tag.

Suggested labels

lgtm, approved, rehearsals-ack

Suggested reviewers

  • eranco74
🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: reverting a previous revert to restore the Go version update for the OSAC installer configuration.
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 This PR modifies only CI configuration YAML files and shell scripts for osac-project, with no changes to any Ginkgo test files.
Test Structure And Quality ✅ Passed PR contains only CI/CD configuration changes (YAML file) with no Ginkgo test code; custom check for test structure/quality is not applicable.
Microshift Test Compatibility ✅ Passed PR only modifies a CI-Operator build config file (updating build_root image tag), not Ginkgo e2e test code. MicroShift compatibility check is not applicable to build configuration changes.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR does not add new Ginkgo e2e tests. It only updates CI configuration YAML for OpenShift build-root image stream tags. Check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only CI-operator build configuration file, updating an image stream tag. No deployment manifests, operator controllers, or scheduling constraints are introduced.
Ote Binary Stdout Contract ✅ Passed PR is purely a CI configuration change (updating a YAML file with image stream tag), containing no source code. OTE Binary Stdout Contract check is not applicable to configuration-only changes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR does not add any Ginkgo e2e tests; it only modifies CI configuration YAML files to update build-root image tags. The custom check is not applicable.
No-Weak-Crypto ✅ Passed PR modifies only CI/CD YAML config file updating Go/OpenShift versions; no weak crypto (MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB) or insecure patterns introduced.
Container-Privileges ✅ Passed PR modifies ci-operator config files only. No K8s/container manifests with privileged settings, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation present.
No-Sensitive-Data-In-Logs ✅ Passed The PR only updates a build root image stream tag in a YAML config file; no logging statements or sensitive data (passwords, tokens, keys, PII) are added or modified.

✏️ 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 requested review from adriengentil and eranco74 May 28, 2026 20:00
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 28, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@omer-vishlitzky: 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-osac-project-osac-installer-main-e2e-vmaas osac-project/osac-installer presubmit Ci-operator config changed
pull-ci-osac-project-osac-installer-main-images osac-project/osac-installer 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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 28, 2026

@omer-vishlitzky: 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.

Copy link
Copy Markdown

@akshaynadkarni akshaynadkarni left a comment

Choose a reason for hiding this comment

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

LGTM

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 28, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akshaynadkarni, omer-vishlitzky

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/osac-project/osac-installer/osac-project-osac-installer-main.yaml`:
- Line 21: The YAML shows a version skew: build_root.image_stream_tag.tag is set
to rhel-9-release-golang-1.26-openshift-5.0 while base_images.origin-cli.name
and releases.latest.candidate.version remain "4.20"; confirm if this is
intentional, and if not update base_images.origin-cli.name and
releases.latest.candidate.version to the matching OpenShift 5.0 values (or the
correct 5.x equivalents) so they align with build_root.image_stream_tag.tag, or
add a clear comment documenting the intentional split; check and apply the same
change for the corresponding keys in the fulfillment-service config as well.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 6e859123-885b-40f7-b215-bae702c8f653

📥 Commits

Reviewing files that changed from the base of the PR and between 45168e9 and c77a0d0.

📒 Files selected for processing (1)
  • ci-operator/config/osac-project/osac-installer/osac-project-osac-installer-main.yaml

name: release
namespace: openshift
tag: rhel-9-release-golang-1.25-openshift-4.21
tag: rhel-9-release-golang-1.26-openshift-5.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check version coordination patterns in similar CI configs

echo "=== Checking other osac-project configs with 5.0 build roots ==="
rg -n 'openshift-5\.0' ci-operator/config/osac-project/ -A5 -B5

echo -e "\n=== Checking if any configs use 5.0 build root with 4.20 releases ==="
fd -e yaml . ci-operator/config/osac-project/ --exec sh -c 'if rg -q "openshift-5\.0" "$1" && rg -q "version.*4\.20" "$1"; then echo "MISMATCH in: $1"; rg -n "tag.*openshift-5\.0|version.*4\.20" "$1"; fi' _ {}

echo -e "\n=== Checking typical version alignment in openshift configs ==="
rg -n 'rhel-9-release-golang-1\.26-openshift-5\.0' ci-operator/config/openshift/ -l | head -5 | while read f; do
  echo "File: $f"
  rg -n 'version:' "$f" | head -3
done

Repository: openshift/release

Length of output: 3234


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== Files with 5.0 build root tag ==="
rg -l 'rhel-9-release-golang-1\.26-openshift-5\.0' ci-operator/config/osac-project/ | cat

for f in $(rg -l 'rhel-9-release-golang-1\.26-openshift-5\.0' ci-operator/config/osac-project/); do
  echo -e "\n=== Inspecting: $f ==="
  echo "--- origin-cli context ---"
  rg -n 'origin-cli' "$f" -C 6 || true

  echo "--- releases latest candidate version context ---"
  rg -n 'releases:|latest:|candidate:|version:\s*"4\.20"' "$f" -C 6 || true

  echo "--- show all version: occurrences (small) ---"
  rg -n 'version:' "$f" | head -20
done

Repository: openshift/release

Length of output: 2310


Fix version skew between build_root (OpenShift 5.0) and releases/base images (4.20)

  • In ci-operator/config/osac-project/osac-installer/osac-project-osac-installer-main.yaml, build_root.image_stream_tag.tag is rhel-9-release-golang-1.26-openshift-5.0, but both base_images.origin-cli.name and releases.latest.candidate.version remain "4.20".
  • The same mismatch exists in ci-operator/config/osac-project/fulfillment-service/osac-project-fulfillment-service-main.yaml.

Confirm whether testing/building intentionally targets 4.20 while using 5.0 build tooling; otherwise, update origin-cli and releases.latest.candidate.version to align with the OpenShift 5.0 build root (or document the intentional split).

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/osac-project/osac-installer/osac-project-osac-installer-main.yaml`
at line 21, The YAML shows a version skew: build_root.image_stream_tag.tag is
set to rhel-9-release-golang-1.26-openshift-5.0 while
base_images.origin-cli.name and releases.latest.candidate.version remain "4.20";
confirm if this is intentional, and if not update base_images.origin-cli.name
and releases.latest.candidate.version to the matching OpenShift 5.0 values (or
the correct 5.x equivalents) so they align with build_root.image_stream_tag.tag,
or add a clear comment documenting the intentional split; check and apply the
same change for the corresponding keys in the fulfillment-service config as
well.

@omer-vishlitzky
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@omer-vishlitzky: 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 May 28, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 39c2f26 into openshift:main May 28, 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. 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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants