When importing the template, specify the template's full path so it doesn't complain about the template resolving to multiple paths
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What happened**:
```
Validation failed {“validation”: “vsphere Provider setup is valid”, “error”: “failed deploying template: govc failed taking vm snapshot: govc: path ‘ubuntu-v1.21.2-kubernetes-1-21-eks-6-amd64-d4be3ee’ resolves to multiple vms\n”, “remediation”: “”}
```
**What you expected to happen**:
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- EKS Anywhere Release:
- EKS Distro Release:
Contributor guide
Research direction
Start by tracing the template import path that produces the govc snapshot error and inspect how the template identifier is passed to govc. Done means importing a template with duplicate names selects the intended full path without the multiple-VM resolution error; the issue provides no file or test names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100