You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.
Hello,
I'm trying out this module in order to automate EdgeGw operations in the future. From what I can see in the monitoring section, there are a few successful login/authorize attempts matching the timestamp of the playbook runs. Yet, no matter what service/operation I request, I get:
- name: vCloudDirectorAnsible
hosts: localhost
tasks:
- name: Do Something
vcd_gateway_services:
host: "{{ VCD_URL }}" # Same as "Site"
user: "{{ VCD_USER }}"
password: "{{ VCD_PASSWORD }}" # Same user-credentials as I login into the GUI
org: "{{ VCD_ORG }}" Same as "Organisation"
vdc: "{{ VCD_ORG_VDC }}" Same as "Datacenter"
api_version: "34.0" # Also tried 33.0, which is also supported, same result
verify_ssl_certs: false
gateway: "edge-gateway"
service: "firewall"
operation: "list"
ansible-playbook -i localhost test.yml
Note that I also tried to create a new NAT-rule using this example, But the result is the same.
Expected behavior
A list of FW-rules, or a new NAT-rule when using the following pattern:
Describe the bug
Hello,
I'm trying out this module in order to automate EdgeGw operations in the future. From what I can see in the monitoring section, there are a few successful login/authorize attempts matching the timestamp of the playbook runs. Yet, no matter what service/operation I request, I get:
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Status code: 400/None, None (request id: 954be739-a291-48da-8270-d945d707eb54)"}
Reproduction steps
pip3 install pyvcloud
ansible-playbook -i localhost test.yml
Note that I also tried to create a new NAT-rule using this example, But the result is the same.
Expected behavior
A list of FW-rules, or a new NAT-rule when using the following pattern:
Additional context
No response
The text was updated successfully, but these errors were encountered: