"ControllerGetVolume" reports "Not Found" is invalid with local storage backend

[zhucan]

Reproduce:

1. deploy the external-provisioner in election-leader mode and with replicatins >=2.
2. disable "ControllerListVolume" capability in hostpath driver.
3. deploy the hostpath driver in daemonset.
4. use "ControllerGetVolume" to get volume'status.
5. deploy the healthe monitor sidecar with election-leader mode.
6. create pvc in the local.

Fix:

1. if the backend storage is local, we should filter the pv with node name. Only monitor the pv in the same node with the sidecar

Suggestion:

1. If backend storege is local disk, Not only "COntrollerGetVolume" or "ControllerListVolume" should monitor the local volume that with the monitor sidecar in the same node.

CC @xing-yang

[xing-yang]

@zhucan How many worker nodes have you deployed?
I don't understand your suggestion. Can you answer the following questions?

• If backend storage is local disk, does "ControllerGetVolume" work?
• If backend storage is local disk, does "ListVolumes" work?

[zhucan]

@xing-yang If only "ControllerGetVolume" enabled, It will get the pv firstly and "GetVolume" from the local disk, but if the volume not exist in the local node(in the other node), it will reports the volume is "Not Found". But the reports is invalid.

[xing-yang]

There's another issue opened to track this and there's already an WIP PR about it.
#87

[xing-yang]

Hi @pohly, do you know if distributed external-provisioner works with CSI hostpath driver? Do we have e2e tests for distributed mode using CSI hostpath driver?

[pohly]

Yes, it works.

There is a separate deployment and a Prow job which uses that deployment.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.