-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Update salt config to allow Debian Jessie on GCE. #25123
Conversation
jlewi
commented
May 4, 2016
As with the existing Wheezy image on GCE, docker is expected to already be installed in the image.
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
2 similar comments
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
I signed it On Tue, May 3, 2016 at 10:32 PM, googlebot notifications@github.com wrote:
|
CLAs look good, thanks! |
GCE e2e build/test passed for commit ccf4b38. |
Automatic merge from submit-queue |
Removing label |
…-#25123-upstream-release-1.2 Automated cherry pick of #25123
@eparis I merged the cherry pick for this PR but the bot hasn't noticed yet (and it's definitely been running according to the bot stats tab on http://cherrypick.k8s.io/#/info). Any ideas why? |
…ry-pick-of-#25123-upstream-release-1.2 Automated cherry pick of kubernetes#25123
…ry-pick-of-#25123-upstream-release-1.2 Automated cherry pick of kubernetes#25123
…ing-listener UPSTREAM: <carry>: apiserver: log new connections during termination Origin-commit: bbf6417825ee2ddf5c44253d5df863192f71a1fa