Skip to content
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

UPSTREAM: 41658: Fix cronjob controller panic on status update failure #13005

Merged
merged 1 commit into from
Feb 19, 2017

Conversation

soltysh
Copy link
Contributor

@soltysh soltysh commented Feb 18, 2017

@smarterclayton you've asked for it

@soltysh
Copy link
Contributor Author

soltysh commented Feb 18, 2017

[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to adb3eb8

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_future/332/) (Base Commit: 6e4333c)

@smarterclayton
Copy link
Contributor

Lgtm [merge]

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to adb3eb8

@openshift-bot
Copy link
Contributor

openshift-bot commented Feb 19, 2017

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_future/342/) (Base Commit: fb6905d) (Image: devenv-rhel7_5939)

@openshift-bot openshift-bot merged commit 0aa6ba1 into openshift:master Feb 19, 2017
@soltysh soltysh deleted the cherrypick_41658 branch February 20, 2017 11:31
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.

3 participants