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

Back porting critical vSphere bug fixes to release 1.3 #31993

Merged

Conversation

dagnello
Copy link
Contributor

@dagnello dagnello commented Sep 2, 2016

vSphere cloud provider plugin was first introduced in Kubernetes 1.3.0. The two PRs listed below contain critical volume attach/detach related fixes. Without these fixes, vSphere in 1.3 lacks the ability to consistently attach/detach volumes correctly especially in a busy cluster.

These changes only affect the vSphere cloud provider.


This change is Reviewable

- Fix unmount for vsanDatastore
- Add support for vsan datastore
@k8s-github-robot k8s-github-robot added do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. release-note-label-needed labels Sep 2, 2016
@k8s-ci-robot
Copy link
Contributor

Can a kubernetes member verify that this patch is reasonable
to test? If so, please reply "ok to test".

Regular contributors should join the org to skip this step.

@brendandburns
Copy link
Contributor

This cherry-pick looks fine to me, it's entirely in the vsphere provider and thus pretty low risk. However, it's also pretty much the time that 1.4 is going to be cut, so it's not 100% clear to me we're going to cut another 1.3.x release.

I'm happy to cherry-pick it into the branch in case we do.

Summoning @smarterclayton and @thockin for their opinions.

@brendandburns
Copy link
Contributor

@k8s-bot ok to test

@thockin
Copy link
Member

thockin commented Sep 6, 2016

I don't think we should let the existence of 1.4 stop us from cutting fixes
to 1.3. We know how long 1.3 took to really stabilize. That said, cutting
and testing releases requires resources...

@fabioy @DavidMcMahon

On Mon, Sep 5, 2016 at 2:50 PM, Kubernetes Bot notifications@github.com
wrote:

GCE e2e build/test passed for commit 5ef05be
5ef05be
.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#31993 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVHFkolTvL-3g_xDyPn_q_MhNhweuks5qnI69gaJpZM4Jz8qx
.

@dagnello
Copy link
Contributor Author

dagnello commented Sep 6, 2016

@brendandburns ./hack/../hack/verify-boilerplate.sh script has failed, it doesn't seem related to this pr:
Error: No such image or container: kube-build-data-f23692ee99

@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.

@smarterclayton
Copy link
Contributor

@kubernetes/rh-storage

@dagnello
Copy link
Contributor Author

dagnello commented Sep 7, 2016

@brendandburns anything else required for this pr?

@brendandburns
Copy link
Contributor

This is ok on my side, given that everyone seems ok w/ it. Cherry-pick approved.

@brendandburns brendandburns added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. release-note Denotes a PR that will be considered when it comes time to generate release notes. cla: human-approved and removed do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. release-note-label-needed labels Sep 8, 2016
@brendandburns
Copy link
Contributor

@dagnello The key error is:

Boilerplate header is wrong for: /go/src/k8s.io/kubernetes/pkg/volume/vsphere_volume/attacher_test.go
Boilerplate header is wrong for: /go/src/k8s.io/kubernetes/pkg/volume/vsphere_volume/attacher.go

Can you check and see what the diff is? My guess is that boilerplate changed between 1.3 and head and you're going to need to manually correct it for what 1.3 expects. (sorry about that)

--brendan

@dagnello dagnello force-pushed the release-1.3_vSphereBugFixes branch from 5ef05be to 465eb83 Compare September 8, 2016 18:14
@dagnello
Copy link
Contributor Author

dagnello commented Sep 8, 2016

@brendandburns thank you, pr has been updated

@k8s-bot
Copy link

k8s-bot commented Sep 8, 2016

GCE e2e build/test passed for commit 465eb83.

@brendandburns brendandburns added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed cla: no labels Sep 9, 2016
@brendandburns
Copy link
Contributor

LGTM.

Thanks

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Sep 12, 2016

GCE e2e build/test passed for commit 465eb83.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 21e7bf5 into kubernetes:release-1.3 Sep 12, 2016
shyamjvs pushed a commit to shyamjvs/kubernetes that referenced this pull request Dec 1, 2016
…BugFixes

Automatic merge from submit-queue

Back porting critical vSphere bug fixes to release 1.3

vSphere cloud provider plugin was first introduced in Kubernetes 1.3.0.  The two PRs listed below contain critical volume attach/detach related fixes.  Without these fixes, vSphere in 1.3 lacks the ability to consistently attach/detach volumes correctly especially in a busy cluster.

These changes only affect the vSphere cloud provider.

- kubernetes#29172
- kubernetes#30535
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. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants