OCPBUGS-55193: data/manifests/bootkube/cvo-overrides: Default to eus-4.14#9643
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@wking: This pull request references OTA-1487 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 story to target the "4.14.z" version, but no target version was set. DetailsIn response to this:
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. |
|
/hold until 2025-04-28, to try to hit the first 4.y.z that could enter |
openshift-ci
bot
added
the
do-not-merge/hold
Like 12e711e (data/manifests/bootkube/cvo-overrides: Default to eus-4.12, 2025-01-15, openshift#9373), but for 4.14. Timing on this one has 4.14 leaving the maintenance phase and entering the EUS phase on 2025-05-01 [1]. We want 4.14.z that enter fast-4.14 up through that time to keep being added to stable-4.14, but 4.14.z that enter fast-4.14 after that date to only be added to eus-4.14 (and no longer get added to stable-4.14), to help folks who don't meet the EUS qualifications stay on releases that they have support for. Landing this change on 2025-04-28 or so should get us into that position, because 4.14.z built the week of 2025-04-21 through 2025-04-25 would likely be entering fast-4.14 on the week of 2025-04-28 through 2025-05-02. [1]: https://access.redhat.com/support/policy/updates/openshift#dates
wking
changed the title
|
@wking: The following tests failed, say
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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon 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 |
openshift-ci
bot
added
the
approved
wking
changed the title
openshift-ci-robot
added
the
jira/severity-moderate
|
@wking: This pull request references Jira Issue OCPBUGS-55193, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
openshift-ci-robot
added
the
jira/invalid-bug
|
/jira refresh |
|
@wking: This pull request references Jira Issue OCPBUGS-55193, which is invalid:
Comment DetailsIn response to this:
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. |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@wking: This pull request references Jira Issue OCPBUGS-55193, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/label cherry-pick-approved |
openshift-ci
bot
added
the
cherry-pick-approved
|
/label backport-risk-assessed |
openshift-ci
bot
added
the
backport-risk-assessed
|
From my opening comment:
And here we are on the 28th :) /hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
openshift-merge-bot
bot
merged commit d92ca63
into
openshift:release-4.14
|
@wking: Jira Issue OCPBUGS-55193: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-55193 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
|
[ART PR BUILD NOTIFIER] Distgit: ose-baremetal-installer |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-artifacts |
|
Fix included in accepted release 4.14.0-0.nightly-2025-04-29-083146 |
Like 12e711e (data/manifests/bootkube/cvo-overrides: Default to eus-4.12, 2025-01-15, openshift#9373) and 6ae7f33 (data/manifests/bootkube/cvo-overrides: Default to eus-4.14, 2025-04-08, openshift#9643), but for 4.16. I'm a bit late this time, with 4.16 already in EUS since the Maintenance phase ended on 2025-12-27: $ 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"}
7 participants
Like 12e711e (#9373), but for 4.14. Timing on this one has 4.14 leaving the maintenance phase and entering the EUS phase on 2025-05-01. We want 4.14.z that enter
fast-4.14up through that time to keep being added tostable-4.14, but4.14.zthat enterfast-4.14after that date to only be added toeus-4.14(and no longer get added tostable-4.14), to help folks who don't meet the EUS qualifications stay on releases that they have support for. Landing this change on 2025-04-28 or so should get us into that position, because 4.14.z built the week of 2025-04-21 through 2025-04-25 would likely be enteringfast-4.14on the week of 2025-04-28 through 2025-05-02.