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.

Sign up for GitHub

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

Jump to bottom

Bump govmomi to v0.27.1 #1276

Closed
saimanoj01 opened this issue Oct 21, 2021 · 0 comments · Fixed by #1280
Closed

Bump govmomi to v0.27.1 #1276

saimanoj01 opened this issue Oct 21, 2021 · 0 comments · Fixed by #1280
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@saimanoj01
Copy link

saimanoj01 commented Oct 21, 2021 •
edited

/kind feature

Describe the solution you'd like
With standard vSphere networking, duplicate port groups can't have the same names in the same network folder. With NSX, portgroups can have the same name in the same switch. In such a scenario where NSX is involved with duplicate portgroup names, using an inventory path results in a MultipleFoundError. govmomi fixed this recently and a new release is cut (v0.27.1) which includes this fix.

Anything else you would like to add:
https://github.com/vmware/govmomi/releases/tag/v0.27.1

Environment:

  • Cluster-api-provider-vsphere version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 21, 2021
@yastij yastij mentioned this issue Oct 26, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

bump govmomi to pickup finding Portgroups by ID yastij/cluster-api-provider-vsphere
2 participants
@saimanoj01 @k8s-ci-robot