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

Automated cherry pick of #23500 #23707

Conversation

bprashanth
Copy link
Contributor

Cherry pick of #23500 on release-1.2.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

@bprashanth
Copy link
Contributor Author

@tam7t asking on googlebots behest (#23707 (comment)), are you ok with cherrypicking your fix to the 1.2 branch?

@bgrant0607
Copy link
Member

@k8s-bot unit test this issue: #IGNORE

@bgrant0607
Copy link
Member

LGTM

@bgrant0607 bgrant0607 added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 31, 2016
@bgrant0607
Copy link
Member

@bprashanth We don't ask for individual permission to copy commits from master to release branches. I'm going to human-approve the CLA.

@k8s-github-robot
Copy link

This PR is not for the master branch but does not have the cherrypick-approved label. Adding the do-not-merge label.

@k8s-github-robot k8s-github-robot added the do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. label Mar 31, 2016
@k8s-github-robot
Copy link

Labelling this PR as size/L

@k8s-github-robot k8s-github-robot added kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 31, 2016
@k8s-bot
Copy link

k8s-bot commented Mar 31, 2016

GCE e2e build/test passed for commit b92de3d6e5918451c76a8c9016ba08a32a520f18.

@bgrant0607
Copy link
Member

@k8s-bot unit test this issue: #IGNORE

@bgrant0607
Copy link
Member

Unit tests fail. PTAL, but this won't make 1.2.1 at this point.

@bgrant0607 bgrant0607 removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 31, 2016
@bprashanth
Copy link
Contributor Author

Got distracted debugging something else. unittests failed because I need to update api ref docs but running update-api-reference.sh (both on master+cherrypick and upstream/release-1.2) didn't fix anything locally, so digging into the script now.

@bprashanth bprashanth force-pushed the automated-cherry-pick-of-#23500-upstream-release-1.2 branch from b92de3d to 842948e Compare March 31, 2016 23:34
@k8s-github-robot k8s-github-robot added this to the v1.2 milestone Mar 31, 2016
@k8s-github-robot k8s-github-robot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 31, 2016
@k8s-github-robot
Copy link

Labelling this PR as size/M

@k8s-github-robot k8s-github-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. release-note-label-needed labels Mar 31, 2016
@k8s-bot
Copy link

k8s-bot commented Apr 1, 2016

GCE e2e build/test passed for commit 842948e.

@bprashanth
Copy link
Contributor Author

@caesarxuchao I think there's something fishy with the update scripts. I ran it against both master + this cherrypick and upstream/release-1.2, it finished successfully, but the "verify-api-ref" script failed. Eventually I ran "verify-api-reference-docs.sh" with the rm line commented out, and copied the files from _tmp over the real ones. This got tests to pass. Maybe bug?

@bprashanth
Copy link
Contributor Author

@bgrant0607 PTAL so we can get this in the next minor release

@bgrant0607
Copy link
Member

Thanks @bprashanth. All green. Merging.

@bgrant0607 bgrant0607 added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 1, 2016
@bgrant0607 bgrant0607 merged commit f54b1bf into kubernetes:release-1.2 Apr 1, 2016
@@ -36,7 +36,7 @@ TMP_ROOT="${KUBE_ROOT}/_tmp"
echo "diffing ${API_REFERENCE_DOCS_ROOT} against freshly generated docs"
ret=0
diff -NauprB -I 'Last update' --exclude=*.md "${API_REFERENCE_DOCS_ROOT}" "${OUTPUT_DIR}" || ret=$?
rm -rf "${TMP_ROOT}"
# rm -rf "${TMP_ROOT}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll add this line back.

I couldn't quickly figure out why the verification failed. I'll help debug when this happens again.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack. didn't mean to comment it out. I assume you're adding it back, let me know if you want me to instead.

shyamjvs pushed a commit to shyamjvs/kubernetes that referenced this pull request Dec 1, 2016
…pick-of-#23500-upstream-release-1.2

Automated cherry pick of kubernetes#23500
shouhong pushed a commit to shouhong/kubernetes that referenced this pull request Feb 14, 2017
…pick-of-#23500-upstream-release-1.2

Automated cherry pick of kubernetes#23500
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants