-
Notifications
You must be signed in to change notification settings - Fork 165
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
Import fails on vsphere when template/-s exist #364
Comments
The above error exists for vsphere version 7.0.3, I just tried to import from older vsphere 6.0.0 and got the same issue:
|
Looks like this error comes from vsphere provider itself: |
If the errors is directly from the Provider it means they intended this type to not be imported when that condition happens, at the end TerraCognita tries to use the provider defined import so there is not much we can do around that. I've checked a bit deeper and there is no specific reason on the PR/Commit in which this was introduced. |
it would be great if we had something to filter in Terracognita, maybe by using regex, we could only import vms which has not any "template" key on it's name, normally vsphere includes templates in the list of VM, by checking this API "/api/vcenter/vm" you can see it. |
Hi, |
Hey, unfortunately not. |
General information:
Terracognita goes fine through all the resources but when it comes to vsphere_virtual_machine and a template is found it exits with an error.
I used this instruction:
Describe the bug:
I am trying to map existing vsphere infra and when I run terracognita specifying all the resources but vsphere_virtual_machine it works perfectly fine.
When I try to discover virtual machines as well it exits with an error.
Log message
All good:
Borked:
The text was updated successfully, but these errors were encountered: