-
Notifications
You must be signed in to change notification settings - Fork 65
Enable 4.4.6 in stable channel(s) #263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/uncc @jwforres @LalatenduMohanty |
|
Hold until tomorrow AM. |
|
/hold cancel |
|
Gone through 16 of the 19 clusters that have been failing for > 1 hour and have not found anything to block this /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jottofar, openshift-bot 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 |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
It has been in stable-4.4 since dc06ce1 (Enable 4.4.6 in stable channel(s), 2020-05-27, openshift#263) landed. Promoting into fast/stable channels for 4.5 makes it clear that we support 4.4.6 regardless of whether a cluster is interested in 4.5 update recommendations or not.
It has been in stable-4.4 since dc06ce1 (Enable 4.4.6 in stable channel(s), 2020-05-27, openshift#263) landed. Promoting into fast/stable channels for 4.5 makes it clear that we support 4.4.6 regardless of whether a cluster is interested in 4.5 update recommendations or not.
4.4.6 has been in stable-4.4 since dc06ce1 (Enable 4.4.6 in stable channel(s), 2020-05-27, openshift#263) landed. Promoting into fast/stable channels for 4.5 makes it clear that we support 4.4.6 regardless of whether a cluster is interested in 4.5 update recommendations or not. And also promote 4.4.8 and 4.4.9 to catch up with 61e8f69 (Enable 4.4.8 in stable channel(s), 2020-06-10, openshift#280) and 64506bb (Enable 4.4.9 in stable channel(s), 2020-06-18, openshift#289).
4.4.6 has been in stable-4.4 since dc06ce1 (Enable 4.4.6 in stable channel(s), 2020-05-27, openshift#263) landed. Promoting into fast/stable channels for 4.5 makes it clear that we support 4.4.6 regardless of whether a cluster is interested in 4.5 update recommendations or not. And also promote 4.4.8 and 4.4.9 to catch up with 61e8f69 (Enable 4.4.8 in stable channel(s), 2020-06-10, openshift#280) and 64506bb (Enable 4.4.9 in stable channel(s), 2020-06-18, openshift#289).
4.4.6 has been in stable-4.4 since dc06ce1 (Enable 4.4.6 in stable channel(s), 2020-05-27, openshift#263) landed. Promoting into fast/stable channels for 4.5 makes it clear that we support 4.4.6 regardless of whether a cluster is interested in 4.5 update recommendations or not. And also promote 4.4.8, 4.4.9, and 4.4.10 to catch up with 61e8f69 (Enable 4.4.8 in stable channel(s), 2020-06-10, openshift#280), 64506bb (Enable 4.4.9 in stable channel(s), 2020-06-18, openshift#289), and 92080fe (Enable 4.4.10 in stable channel(s), 2020-06-24, openshift#296).
Please merge within 48 hours of https://errata.devel.redhat.com/advisory/55013 shipping live OR a Cincinnati-first release.
This should provide adequate soak time for fast channel PR #262