Skip to content

Add missing Cincinnati channel files for OKD SCOS releases - #18

Closed
redhat-chai-bot wants to merge 1 commit into
okd-project:mainfrom
redhat-chai-bot:sync-cincinnati-channels-2026-10-22
Closed

redhat-chai-bot wants to merge 1 commit into
okd-project:mainfrom
redhat-chai-bot:sync-cincinnati-channels-2026-10-22

Conversation

@redhat-chai-bot

Copy link
Copy Markdown
Contributor

Add 7 new Cincinnati channel files for OKD SCOS releases that are present on the OKD release controller but were missing from the graph data.

Streams Analyzed

  • 5-scos-next — candidate releases for OKD 5.x
  • 5-scos-stable — stable releases for OKD 5.x
  • 4-scos-next — candidate releases for OKD 4.x
  • 4-scos-stable — stable releases for OKD 4.x

Existing Channels (already up to date, not modified)

  • candidate-5.0.yaml — 5.0 candidate releases (ec.0–ec.10)
  • stable-5.0.yaml — 5.0 stable releases (.0–.3)
  • stable-4.22.yaml — 4.22 stable releases (.0–.10)
  • stable-4.21.yaml — 4.21 stable releases (.0–.11)
  • stable-4.20.yaml — 4.20 stable releases (.0–.17)

New Channels Added

File Previous (upgrade entry point) Current versions
candidate-5.1.yaml 5.0.0-okd-scos.ec.10 5.1.0-okd-scos.ec.0
candidate-4.22.yaml 4.21.0-okd-scos.ec.19 ec.1–ec.16 (12 releases)
candidate-4.21.yaml 4.20.0-okd-scos.17 (stable¹) ec.2–ec.19 (11 releases)
stable-4.19.yaml 4.18.0-okd-scos.10 .7–.19 (13 releases)
stable-4.18.yaml 4.17.0-okd-scos.3 .0–.10 (11 releases)
stable-4.17.yaml 4.16.0-okd-scos.1 .0–.3 (4 releases)
stable-4.16.yaml (none — root of SCOS chain) .0–.1 (2 releases)

¹ No 4.20 candidate releases exist on the release controller; the latest 4.20 stable release is used as the upgrade entry point.

Notes

  • Only Accepted releases from the OKD release controller are included.
  • stable-4.16 is the root of the SCOS stable channel chain — there are no 4.15 SCOS stable releases to serve as a previous version. The filter pattern conventionally includes 4.15 for consistency.
  • Some candidate version numbers are non-sequential (e.g., ec.1, ec.2, ec.3, ec.4, ec.6 — skipping ec.5) because only Accepted releases are included; Rejected/Failed releases are excluded.
  • No existing channel files were modified.

AI-generated. Review for accuracy.

Automated by scheduled task okd_cincinnati_graph_data_sync (instructions: config/groups/openshift-core/personas/okd_assistant/scheduled_tasks/okd_cincinnati_graph_data_sync.md, run: b80b9758cf66485e9a36209acd4e7451, commit: fe73eb5dd)

Add 7 new channel files for OKD SCOS releases that were present
on the release controller but missing from the graph data:

- candidate-5.1: 5.1.0-okd-scos.ec.0
- candidate-4.22: 4.22 candidate releases (ec.1 through ec.16)
- candidate-4.21: 4.21 candidate releases (ec.2 through ec.19)
- stable-4.19: 4.19 stable releases (.7 through .19)
- stable-4.18: 4.18 stable releases (.0 through .10)
- stable-4.17: 4.17 stable releases (.0 through .3)
- stable-4.16: 4.16 stable releases (.0 through .1)
@redhat-chai-bot
redhat-chai-bot force-pushed the sync-cincinnati-channels-2026-10-22 branch from 4da7b6a to fd410e0 Compare October 22, 2026 20:12
@jatinsu

jatinsu commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

OKD Cincinnati doesn't support versions below OKD 5.0

@jatinsu jatinsu closed this Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants