NO-ISSUE: channels/stable-4.1[6-8]: 4.16 is into it's EUS phase by wking · Pull Request #8709 · openshift/cincinnati-graph-data

wking · 2026-01-31T00:41:59Z

Generated with:

$ hack/release-end-of-maintenance.sh 4.16

to catch up with the earlier 2025-12-27 transition:

$ curl -s 'https://access.redhat.com/product-life-cycles/api/v1/products?name=OpenShift+Container+Platform' | jq -c '.data[].versions[] | select(.name == "4.16").phases[]'
{"name":"General availability","date":"2024-06-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Full support","date":"2025-01-01T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Maintenance support","date":"2025-12-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Extended update support","date":"2026-06-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Extended update support Term 2","date":"2027-06-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Extended update support Term 3","date":"N/A","date_format":"string","additional_text":""}
{"name":"Extended life phase","date":"N/A","date_format":"string"}

The delay here was waiting for openshift/installer@be845abbc0 (openshift/installer#10226) to make it into a 4.16.z, and it's in 4.16.56. While the older, stable-4.16 default 4.16.55 has almost made it through to all the stable changel it was aiming for:

$ git grep 4.16.55 channels
channels/candidate-4.16.yaml:- 4.16.55
channels/candidate-4.17.yaml:- 4.16.55
channels/candidate-4.18.yaml:- 4.16.55
channels/eus-4.16.yaml:- 4.16.55
channels/fast-4.16.yaml:- 4.16.55
channels/fast-4.17.yaml:- 4.16.55
channels/stable-4.16.yaml:- 4.16.55
channels/stable-4.17.yaml:- 4.16.55

It still needs a new 4.18.z to be built before it gets into stable-4.18. There isn't even one in candidate-4.18 yet:

$ hack/show-edges.py --cincinnati https://api.openshift.com/api/upgrades_info/graph --root-version 4.16.55 candidate-4.18
4.16.55 -> 4.16.56
4.16.55 -> 4.17.47

But we can't wait for that new 4.18.z to cook all the way through to stable-4.18, because the eus-4.16 default 4.16.56 would have cooked into stable-* by then. So land this transition now, and we'll come back around later and manually add 4.16.55 to stable-4.18 later.

Generated with: $ hack/release-end-of-maintenance.sh 4.16 to catch up with the earlier 2025-12-27 transition: $ curl -s 'https://access.redhat.com/product-life-cycles/api/v1/products?name=OpenShift+Container+Platform' | jq -c '.data[].versions[] | select(.name == "4.16").phases[]' {"name":"General availability","date":"2024-06-27T00:00:00.000Z","date_format":"date","additional_text":""} {"name":"Full support","date":"2025-01-01T00:00:00.000Z","date_format":"date","additional_text":""} {"name":"Maintenance support","date":"2025-12-27T00:00:00.000Z","date_format":"date","additional_text":""} {"name":"Extended update support","date":"2026-06-27T00:00:00.000Z","date_format":"date","additional_text":""} {"name":"Extended update support Term 2","date":"2027-06-27T00:00:00.000Z","date_format":"date","additional_text":""} {"name":"Extended update support Term 3","date":"N/A","date_format":"string","additional_text":""} {"name":"Extended life phase","date":"N/A","date_format":"string"} The delay here was waiting for openshift/installer@be845abbc0 (data/manifests/bootkube/cvo-overrides: Default to eus-4.16, 2026-01-15, openshift/installer#10226) to make it into a 4.16.z, and it's in 4.16.56 [1]. While the older, stable-4.16 default 4.16.55 has almost made it through to all the stable changel it was aiming for: $ git grep 4.16.55 channels channels/candidate-4.16.yaml:- 4.16.55 channels/candidate-4.17.yaml:- 4.16.55 channels/candidate-4.18.yaml:- 4.16.55 channels/eus-4.16.yaml:- 4.16.55 channels/fast-4.16.yaml:- 4.16.55 channels/fast-4.17.yaml:- 4.16.55 channels/stable-4.16.yaml:- 4.16.55 channels/stable-4.17.yaml:- 4.16.55 It still needs a new 4.18.z to be built before it gets into stable-4.18. There isn't even one in candidate-4.18 yet: $ hack/show-edges.py --cincinnati https://api.openshift.com/api/upgrades_info/graph --root-version 4.16.55 candidate-4.18 4.16.55 -> 4.16.56 4.16.55 -> 4.17.47 But we can't wait for that new 4.18.z to cook all the way through to stable-4.18, because the eus-4.16 default 4.16.56 would have cooked into stable-* by then. So land this transition now, and we'll come back around later and manually add 4.16.55 to stable-4.18 later. [1]: https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4.16.56

openshift-ci-robot · 2026-01-31T00:42:03Z

@wking: This pull request explicitly references no jira issue.

Details

In response to this:

Generated with:
$ hack/release-end-of-maintenance.sh 4.16
to catch up with the earlier 2025-12-27 transition:
$ curl -s 'https://access.redhat.com/product-life-cycles/api/v1/products?name=OpenShift+Container+Platform' | jq -c '.data[].versions[] | select(.name == "4.16").phases[]'
{"name":"General availability","date":"2024-06-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Full support","date":"2025-01-01T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Maintenance support","date":"2025-12-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Extended update support","date":"2026-06-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Extended update support Term 2","date":"2027-06-27T00:00:00.000Z","date_format":"date","additional_text":""}
{"name":"Extended update support Term 3","date":"N/A","date_format":"string","additional_text":""}
{"name":"Extended life phase","date":"N/A","date_format":"string"}
The delay here was waiting for openshift/installer@be845abbc0 (openshift/installer#10226) to make it into a 4.16.z, and it's in 4.16.56. While the older, stable-4.16 default 4.16.55 has almost made it through to all the stable changel it was aiming for:
$ git grep 4.16.55 channels
channels/candidate-4.16.yaml:- 4.16.55
channels/candidate-4.17.yaml:- 4.16.55
channels/candidate-4.18.yaml:- 4.16.55
channels/eus-4.16.yaml:- 4.16.55
channels/fast-4.16.yaml:- 4.16.55
channels/fast-4.17.yaml:- 4.16.55
channels/stable-4.16.yaml:- 4.16.55
channels/stable-4.17.yaml:- 4.16.55
It still needs a new 4.18.z to be built before it gets into stable-4.18. There isn't even one in candidate-4.18 yet:
$ hack/show-edges.py --cincinnati https://api.openshift.com/api/upgrades_info/graph --root-version 4.16.55 candidate-4.18
4.16.55 -> 4.16.56
4.16.55 -> 4.17.47
But we can't wait for that new 4.18.z to cook all the way through to stable-4.18, because the eus-4.16 default 4.16.56 would have cooked into stable-* by then. So land this transition now, and we'll come back around later and manually add 4.16.55 to stable-4.18 later.

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 · 2026-01-31T00:42:09Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

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

openshift-ci · 2026-01-31T00:52:29Z

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

DavidHurta

/hold

Thanks for the detailed description! 🙇

Changes look good. Holding due to my sole comment.

DavidHurta · 2026-02-02T15:27:15Z

@@ -1,6 +1,6 @@
 feeder:
  delay: PT0H
-  filter: 4[.](16|17|18)[.][0-9].*


So land this transition now, and we'll come back around later and manually add 4.16.55 to stable-4.18 later.

Do we have a Jira to track this? If not, I am happy to create one. To make sure that the version is added.

No Jira yet, I just set myself a reminder to start checking again in a few weeks, after which I'll poll weekly. I have no problem with you creating a Jira if you like.

I have created https://issues.redhat.com/browse/OTA-1852. I have assigned it to me so that I can practice a bit on these graph-data thingies, if that works for everyone.

We can also assign it to anyone else.

openshift-ci · 2026-02-02T15:30:45Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidHurta, wking

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:

~~OWNERS~~ [DavidHurta,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

DavidHurta · 2026-02-02T17:25:15Z

/unhold

As described in 16cb1cb (channels/stable-4.1[6-8]: 4.16 is into it's EUS phase, 2026-01-27, openshift#8709), we had to drop the 'feeder' for 4.16.z to keep the EUS-phase 4.16.56 out of stable-* before 4.16.55 had quite percolated through to all its appropriate stable-* channels. This commit manually finishes off 4.16.55, now that there's a newer stable 4.18.z release to update to (and there has been for a month, since 4.18.32 was itself manually promoted to stale-4.18): $ git blame --first-parent channels/stable-4.18.yaml | tail -n2 023497c (Scott Dodson 2026-02-03 10:27:27 -0500 140) - 4.18.32 c105cbe (openshift-merge-bot[bot] 2026-02-18 07:33:44 +0000 141) - 4.18.33 $ hack/show-edges.py --cincinnati https://api.openshift.com/api/upgrades_info/graph --root-version 4.16.55 candidate-4.18 | grep ' 4[.]18[.]' | sort -V | head -n1 4.17.47 -> 4.18.32

As described in 16cb1cb (channels/stable-4.1[6-8]: 4.16 is into it's EUS phase, 2026-01-27, openshift#8709), we had to drop the 'feeder' for 4.16.z to keep the EUS-phase 4.16.56 out of stable-* before 4.16.55 had quite percolated through to all its appropriate stable-* channels. This commit manually finishes off 4.16.55, now that there's a newer stable 4.18.z release to update to (and there has been for a month, since 4.18.32 was itself manually promoted to stable-4.18): $ git blame --first-parent channels/stable-4.18.yaml | tail -n2 023497c (Scott Dodson 2026-02-03 10:27:27 -0500 140) - 4.18.32 c105cbe (openshift-merge-bot[bot] 2026-02-18 07:33:44 +0000 141) - 4.18.33 $ hack/show-edges.py --cincinnati https://api.openshift.com/api/upgrades_info/graph --root-version 4.16.55 candidate-4.18 | grep ' 4[.]18[.]' | sort -V | head -n1 4.17.47 -> 4.18.32

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 31, 2026

openshift-ci Bot requested review from DavidHurta and fao89 January 31, 2026 00:42

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2026

DavidHurta approved these changes Feb 2, 2026

View reviewed changes

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 2, 2026

openshift-ci Bot assigned DavidHurta Feb 2, 2026

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

openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 2, 2026

openshift-merge-bot Bot merged commit 0daef27 into openshift:master Feb 2, 2026
3 checks passed

wking deleted the 4.16-end-of-maintenance branch February 2, 2026 20:42

wking mentioned this pull request Mar 3, 2026

OTA-1852: channels/stable-4.18: Manually promote 4.16.55 #8912

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

NO-ISSUE: channels/stable-4.1[6-8]: 4.16 is into it's EUS phase#8709

NO-ISSUE: channels/stable-4.1[6-8]: 4.16 is into it's EUS phase#8709
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
wking:4.16-end-of-maintenance

wking commented Jan 31, 2026

Uh oh!

openshift-ci-robot commented Jan 31, 2026

Uh oh!

coderabbitai Bot commented Jan 31, 2026

Review skipped

Uh oh!

openshift-ci Bot commented Jan 31, 2026

Uh oh!

DavidHurta left a comment

Uh oh!

DavidHurta Feb 2, 2026

Uh oh!

wking Feb 2, 2026

Uh oh!

DavidHurta Feb 2, 2026

Uh oh!

DavidHurta Feb 2, 2026

Uh oh!

openshift-ci Bot commented Feb 2, 2026

Uh oh!

DavidHurta commented Feb 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

wking commented Jan 31, 2026

Uh oh!

openshift-ci-robot commented Jan 31, 2026

Uh oh!

coderabbitai Bot commented Jan 31, 2026

Review skipped

Uh oh!

openshift-ci Bot commented Jan 31, 2026

Uh oh!

DavidHurta left a comment

Choose a reason for hiding this comment

Uh oh!

DavidHurta Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

wking Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

DavidHurta Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

DavidHurta Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented Feb 2, 2026

Uh oh!

DavidHurta commented Feb 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants