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

regression: vm clone failed #1712

Closed
nanw1103 opened this issue Nov 15, 2019 · 3 comments · Fixed by #1714
Closed

regression: vm clone failed #1712

nanw1103 opened this issue Nov 15, 2019 · 3 comments · Fixed by #1714

Comments

@nanw1103
Copy link

nanw1103 commented Nov 15, 2019

Command being used:
govc vm.clone -waitip=true -on=true -vm /nanw/vm/hlcm-build/hlcm-deployer-build-base hlcm-deployer

Works with 0.21
Fails with: v0.21.0-58-g8d28646
Fails with: master build 0.22

Error message in vCenter:
Task Name: Call DRS for cross vMotion placement recommendations
Status: The operation is not allowed in the current state.

I think this is related to the target cluster state, which has one and only one host without DRS enabled.

@dougm
Copy link
Member

dougm commented Nov 15, 2019

What environment variables do you have set? In this case, if GOVC_CLUSTER is set, that could be the issue. That is the only related change to vm.clone since 0.21: #1589

Either way, I think we'll need to use a different flag name or ignore the env var to include the placement feature that #1589 introduced, so we avoiding changing behavior if GOVC_CLUSTER was already set.

dougm added a commit to dougm/govmomi that referenced this issue Nov 15, 2019
PR vmware#1589 added the '-cluster' flag to vm.clone and vm.create commands.
However, the GOVC_CLUSTER env var should not be used as a default.

Fixes vmware#1712
@dougm
Copy link
Member

dougm commented Nov 15, 2019

#1714 should fix the issue for you.

Copy link
Contributor

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants