-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
fix azure disk mounter issue #52260
fix azure disk mounter issue #52260
Conversation
Hi @andyzhangx. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/sig azure |
@feiskyer for your interest |
/ok-to-test |
pkg/volume/azure_dd/azure_mounter.go
Outdated
@@ -79,7 +79,8 @@ func (m *azureDiskMounter) SetUpAt(dir string, fsGroup *int64) error { | |||
return err | |||
} | |||
if !mountPoint { | |||
return fmt.Errorf("azureDisk - Not a mounting point for disk %s on %s", diskName, dir) | |||
glog.V(2).Infof("azureDisk - already mounted to target %s", dir) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't log or V(4)
change loginfo level from 2 to 4
b461a01
to
2a9cb38
Compare
/test pull-kubernetes-federation-e2e-gce |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx, brendandburns Associated issue: 52261 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 52452, 52115, 52260, 52290) |
@jdumars This PR should be cherry picked to v1.7, v.18, do you know who will do this? Thanks. |
@andyzhangx You could file cherry-pick PRs yourself, or I can help if you'd like. |
v1.8 cherry pick is not required because it is still in code freeze period. |
@andyzhangx feiskyer is correct - this will be in 1.8, and you use the cherry pick tool to do the other two. Contact @wojtek-t for 1.7.x and @enisoc for 1.6.x |
Removing 1.8 milestone as this was committed to 1.8 branch before 1.8.0 release. |
What this PR does / why we need it:
fix azure disk mounter issue, it's a P1 bug, it exists in 1.7, 1.8 release, should cherry pick to 1.7, 1.8
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #fixes #52261
consider following issue:
4d 1m 3065 kubelet, 14777acs9000 Warning FailedMount MountVolume.SetUp failed for volume "pvc-7a0cdeb9-92c7-11e7-b86b-000d3a36d70c" : azureDisk - No
t a mounting point for disk andykubewin175-dynamic-pvc-7a0cdeb9-92c7-11e7-b86b-000d3a36d70c on \var\lib\kubelet\pods\d146c023-92c7-11e7-b86b-000d3a36d70c\volumes\kubernetes.io~azure-disk\pvc-7a0cdeb9-92c7-11
e7-b86b-000d3a36d70c
4d 1m 3157 kubelet, 14777acs9000 Warning FailedMount Error syncing pod
Special notes for your reviewer:
If you take a look at following implementation of vsphere or gce, it will return nil instead of error:
https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/vsphere_volume/vsphere_volume.go#L217-L220
https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/gce_pd/gce_pd.go#L273-L275
The logic of return info parsing here, it's wrong to return error
https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/util/operationexecutor/operation_generator.go#L469-L475
Release note: