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

list-volume fails in multi-vcenter environment if all nodes are in only one vcenter #2393

Closed
Mattes83 opened this issue May 23, 2023 · 1 comment · Fixed by #2395
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Mattes83
Copy link
Contributor

/kind bug

What happened:
list-volume fails in multi-vcenter environment if there are only nodes in one vcenter.
The call to Retrieve should not be made if there are no properties to retrieve.

What you expected to happen:
The call to Retrieve should be skipped.

How to reproduce it (as minimally and precisely as possible):
Add two VirtualCenter entries to csi-vsphere.conf, but only have nodes in one VirtualCenter.

Anything else we need to know?:
I stumbled on this when migrating to a multi-vcenter setup.

Environment:

  • csi-vsphere version: 3.0.1
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label May 23, 2023
@gohilankit
Copy link
Contributor

@Mattes83 Can you paste the error logs you were getting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants