Files
vmware-api-simulator/docs/examples/troubleshooting-clients.md
T
inecs f8d3cbdd59 Initial commit: VMware vSphere API simulator scaffold.
Add the FastAPI app, PostgreSQL migrations, Docker/Helm packaging, API
contracts, docs, client examples, and the unit/integration/compatibility
test suite for local client and tooling labs without a real vCenter.
2026-07-18 04:42:11 +03:00

1.4 KiB

Language / Язык: English | Русский

Troubleshooting clients

Symptom Fix
TLS certificate errors Use :443 with verify=False / insecure/allow_unverified_ssl=true only locally, or use plain HTTP :80
401 on first call Send Authorization: Basic … only to /api/session (or SOAP Login); every other call needs vmware-api-session-id
403 on power/create You may be using readonly@vsphere.local — switch to administrator@vsphere.local or operator@vsphere.local
VM not found small seed VM names are web-01, web-02, db-01, app-01, jumpbox — not Proxmox-style numeric VMIDs
Create returns a MOID, not a task REST POST /api/vcenter/vm returns the new VM's MOID synchronously; only power/clone/relocate/snapshot/OVF-deploy return { "task": "…" }
Provider create vs task Poll /api/cis/tasks/{task}; many providers (Terraform, Pulumi) already wait internally — raw HTTP/Go/Java/Perl clients often forget to
Drift after reseed Refresh/recreate Terraform/Pulumi/Ansible state after make seed
Session expired mid-run Sessions have a 2-hour sliding TTL; re-login if a long-running script idles past that
SOAP Login fails Confirm the envelope targets /sdk with SOAPAction set (empty string is fine) and Content-Type: text/xml