Re-factored script for Cross VC vMotion via API error when running
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 951
- Forks
- 504
- PR merge metrics
- No merged PRs in 30d
Description
When running the script the below error gets logged:
Wait-Task : 2017-02-23 08:37:28 AM Wait-Task The operation for the
entity "ubuntu-iperf_01" failed with the following message: "A specified
parameter was not correct: ServiceLocator.instanceUuid"
At D:\xmove.ps1:151 char:14
-
$task1 | Wait-Task -Verbose -
~~~~~~~~~~~~~~~~~~- CategoryInfo : NotSpecified: (:) [Wait-Task], InvalidArgument
- FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpda
tes_OperationFailed,VMware.VimAutomation.ViCore.Cmdlets.Commands.WaitTask
A couple of users commented the they fixed the issue by doing the below:
Line 101: $service.instanceUuid = $destVCConn.InstanceUuid.ToUpper()
After adding .ToUpper() the script runs through properly. Could you perhaps update the script if this is the correct fix?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open xmove.ps1 and inspect the destination connection assignment around line 101, then review the Wait-Task call at line 151 and the reported ServiceLocator.instanceUuid error. Confirm the requested value handling fixes the Cross VC vMotion run, and verify that the script completes without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100