Skip to content

Conversation

@openshift-bot
Copy link
Contributor

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

@openshift-bot openshift-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 27, 2020
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 30, 2020
@sdodson sdodson force-pushed the pr-stable-4.4.6 branch from d66e6a6 to dc06ce1 Compare June 2, 2020 16:33
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 2, 2020
@sdodson
Copy link
Member

sdodson commented Jun 4, 2020

/uncc @jwforres @LalatenduMohanty
/assign @jottofar

@sdodson
Copy link
Member

sdodson commented Jun 4, 2020

Hold until tomorrow AM.

@sdodson
Copy link
Member

sdodson commented Jun 5, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 5, 2020
@jottofar
Copy link
Contributor

jottofar commented Jun 5, 2020

Gone through 16 of the 19 clusters that have been failing for > 1 hour and have not found anything to block this

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 5, 2020
@openshift-ci-robot
Copy link

[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

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 5, 2020
@jottofar
Copy link
Contributor

jottofar commented Jun 5, 2020

/retest

@openshift-bot
Copy link
Contributor Author

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor Author

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor Author

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 01bc99e into master Jun 5, 2020
wking added a commit to wking/cincinnati-graph-data that referenced this pull request Jun 6, 2020
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.
wking added a commit to wking/cincinnati-graph-data that referenced this pull request Jul 1, 2020
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.
wking added a commit to wking/cincinnati-graph-data that referenced this pull request Jul 1, 2020
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).
wking added a commit to wking/cincinnati-graph-data that referenced this pull request Jul 1, 2020
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).
wking added a commit to wking/cincinnati-graph-data that referenced this pull request Jul 1, 2020
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).
@sdodson sdodson deleted the pr-stable-4.4.6 branch October 12, 2020 16:49
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants