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

Can't get vSphere provider to work #348

Open
fabricesemti80 opened this issue Feb 27, 2023 · 1 comment
Open

Can't get vSphere provider to work #348

fabricesemti80 opened this issue Feb 27, 2023 · 1 comment
Labels
Type: Bug Something isn't working

Comments

@fabricesemti80
Copy link

General information:

I tried to run Terracognita via a Makefile (also via Docker) with the following input:

VSPHERE_SERVER := <vshpere server address>
VSPHERE_USER := [email protected]
VSPHERE_PASSWORD := <vsphere admin pw>
VSPHERE_SOAP_URL :=<vshpere server SOAP address>
# Get-AdvancedSetting -Entity $global:DefaultVIServer -Name "config.vpxd.sso.sts.uri" | Select-Object -ExpandProperty Value

# Define targets
.PHONY: tc
tc:
	terracognita vsphere --tfstate current.tfstate --debug --soap-url ${VSPHERE_SOAP_URL} --username ${VSPHERE_USER} --password ${VSPHERE_PASSWORD}
  • Operating System:
    Windows 11 / WSL2 / Ubuntu
  • Terracognita version / tag:
terracognita version
The current version is: v0.8.1
  • Did you build Terracognita from sources or did you use the Docker image:
    used brew

Describe the bug:

Command errored out with:

ns0:InvalidSecurity: There is no Security element in the soap header

A clear and concise description of what the bug is.

Log message

Here you can paste the log message or paste the link to console logs. If the log message is too big, you can use a tool like https://pastebin.com/.

Additional context

Add any other context about the problem here.

@fabricesemti80 fabricesemti80 added the Type: Bug Something isn't working label Feb 27, 2023
@xescugc
Copy link
Member

xescugc commented Apr 13, 2023

Could you provide a bit more of the actual log from TerraCognita? So I could pinpoint more precisely which of the calls to VSphere is failing, because with in our usecase it works fine so it may be missing some configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants