Cross vCenter v-motion error
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 951
- Forks
- 504
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I've got this error:
Wait-Task : 2017-04-11 3:48:37 PM Wait-Task The operation for the entity "DB0106" failed with the following message: "Cannot complete login due to an incorrect user name or password."
At E:\Scripts-Migration\xVC-migrate-vm.ps1:165 char:14
-
$task1 | Wait-Task -Verbose -
~~~~~~~~~~~~~~~~~~- CategoryInfo : NotSpecified: (:) [Wait-Task], InvalidLogin
- FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed,VMware.VimAutomation.ViCore.Cmdlets.Commands.WaitTask
I have verified the login account for both vcenters are correct and I can connect both vCenters without any problem. what could be the cause?
Best Regards.
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
Start with the reported Wait-Task invocation at line 165 of xVC-migrate-vm.ps1 and review the cross-vCenter migration setup leading to it. Reproduce the InvalidLogin failure using the verified vCenter connections; done means identifying and documenting the cause of the task login failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100