test: use env var for smb server configuration

[Phaow]

What type of PR is this?
/kind failing-test

What this PR does / why we need it:

• Fixed run the e2e test locally the smbDriver nil pointer issue
• Use env var for smb server configuration to make e2e test execute in different test clusters more flexibility.
• Use obvious mountOption in case to make e2e test could be executed in some different smb server configurations

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

none

[linux-foundation-easycla]

• ✅login: Phaow / (6e93ede)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @Phaow!

It looks like this is your first PR to kubernetes-csi/csi-driver-smb 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/csi-driver-smb has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Phaow. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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-sigs/prow repository.

[Phaow]

Hi @andyzhangx , could you please help take a look when you get a chance? Thank you!

[andyzhangx]

/ok-to-test

[coveralls]

Pull Request Test Coverage Report for Build 8977925603

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 79.293%

---

Totals
Change from base Build 8832986014:	0.0%
Covered Lines:	942
Relevant Lines:	1188

---

💛 - Coveralls

[andyzhangx]

/retest

[Phaow]

/test pull-csi-driver-smb-sanity

[Phaow]

/retest-required

[Phaow]

/retest-required

[Phaow]

/test pull-csi-driver-smb-sanity

[Phaow]

It's a bit strange, I could execute the sanity-test on my local successfully. In the failure job logs always failed to get metrics: failed to get FsInfo due to error resource temporarily unavailable. The PR does not modify any driver itself codes should have no influence with the sanity-test results. @andyzhangx Do you happen to know something about this? Is there I missed something?

$ make sanity-test
------------------------------

Ran 37 of 78 Specs in 4.751 seconds
SUCCESS! -- 37 Passed | 0 Failed | 1 Pending | 40 Skipped
pkill -f smbplugin
Deleting CSI sanity test binary
Uninstalling samba server on localhost
samba

[andyzhangx]

/retest

[Phaow]

/retest

[Phaow]

/test pull-csi-driver-smb-sanity

[k8s-ci-robot]

@Phaow: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-csi-driver-smb-sanity	6e93ede	link	true	/test pull-csi-driver-smb-sanity

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

[andyzhangx]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [andyzhangx]

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