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

fix: smb valid path error #95583

Merged
merged 1 commit into from Oct 16, 2020
Merged

Conversation

andyzhangx
Copy link
Member

@andyzhangx andyzhangx commented Oct 15, 2020

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: smb valid path error, ported from kubernetes/utils#188

isValidPath func error should be ignored since if password changed, it would return following access error:

PathValid(\\xxx\share) failed with returned output: Test-Path : Access is denied

By that case, should remove original SMB remote path and mount again.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
/assign @jingxu97

Does this PR introduce a user-facing change?:

fix: smb valid path error

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

fix: smb valid path error

/priority important-soon
/sig storage
/triage accepted

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. sig/storage Categorizes an issue or PR as relevant to SIG Storage. triage/accepted Indicates an issue or PR is ready to be actively worked on. release-note Denotes a PR that will be considered when it comes time to generate release notes. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 15, 2020
@andyzhangx
Copy link
Member Author

/retest

@andyzhangx
Copy link
Member Author

@jingxu97 looks like the flush disk operation did not fix the data corruption issue on Windows:

/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:587
Unexpected error:
    <*errors.errorString | 0xc0003b06c0>: {
        s: "Failed to find \"hello world\r\nhello world\r\n\", last result: \"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00hello world\r\n\"",
    }
    Failed to find "hello world
    hello world
    ", last result: "�������������hello world
    "
occurred
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:637

@andyzhangx
Copy link
Member Author

/test pull-kubernetes-e2e-azure-disk-windows

1 similar comment
@andyzhangx
Copy link
Member Author

/test pull-kubernetes-e2e-azure-disk-windows

@jingxu97
Copy link
Contributor

@jingxu97 looks like the flush disk operation did not fix the data corruption issue on Windows:

/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:587
Unexpected error:
    <*errors.errorString | 0xc0003b06c0>: {
        s: "Failed to find \"hello world\r\nhello world\r\n\", last result: \"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00hello world\r\n\"",
    }
    Failed to find "hello world
    hello world
    ", last result: "�������������hello world
    "
occurred
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:637

So this test already has the fix I assume? My test failed mostly with empty file like ""\x00\x00\x00\x00\x00\x00\x..." without having the hello world context at all. The tetst is creating a pod with a volume, delete it, and create a second one to read the context. What your test is doing?

@andyzhangx
Copy link
Member Author

/testsuites/testsuites.g

@jingxu97 it's create a deployment object, write and read to it, delete the pod and write and read to it again, looks like it's the same

@andyzhangx
Copy link
Member Author

/test pull-kubernetes-e2e-azure-disk-windows

@andyzhangx
Copy link
Member Author

/testsuites/testsuites.g

@jingxu97 it's create a deployment object, write and read to it, delete the pod and write and read to it again, looks like it's the same

it's a random failure as you could see @jingxu97

@jingxu97
Copy link
Contributor

/testsuites/testsuites.g

@jingxu97 it's create a deployment object, write and read to it, delete the pod and write and read to it again, looks like it's the same

it's a random failure as you could see @jingxu97

y, it is random. But it always happen if you run a number of times. I remember after adding writevolumecache call, it will not happen again for my case.

@andyzhangx
Copy link
Member Author

@jingxu97 could you review this PR? thanks.

@jingxu97
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 16, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, jingxu97

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 16, 2020
@k8s-ci-robot k8s-ci-robot merged commit 9af86e8 into kubernetes:master Oct 16, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants