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

[BUG] Guest network name on VM changes on restarting vcenter #2552

Closed
abansal4032 opened this issue Aug 18, 2021 · 2 comments
Closed

[BUG] Guest network name on VM changes on restarting vcenter #2552

abansal4032 opened this issue Aug 18, 2021 · 2 comments
Labels
lifecycle/stale

Comments

@abansal4032
Copy link

Describe the bug
A running VMs guest network name is changed and set to SwitchUuid of the VM if the underlying vcenter is restarted/upgraded.

To Reproduce
Steps to reproduce the behavior:

  1. Create a VM
  2. Restart/upgrade the vcenter server
  3. The VMs guest network name is changed
  4. Restart the VM
  5. The VM gets back the correct value of the network name

Expected behavior
The Guest network name should not be changed on vcenter upgrade/restart.

Affected version
govmomi: v0.23.1
vcenter: 6.7

Additional context
This might be an issue from the vcenter server itself. The same behavior of incorrect network name was observed with a govc client.
@github-actions
Copy link
Contributor

Howdy 🖐   abansal4032 ! Thank you for your interest in this project. We value your feedback and will respond soon.

If you want to contribute to this project, please make yourself familiar with the CONTRIBUTION guidelines.

@github-actions
Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abansal4032