This is my ansible playbook:
Which I then run using
Which is strange because if I run this playbook against my production proxmox server I get a different error.
YAML:
---
- hosts: gluster-test
become: true
tasks:
- name: Create new VM with minimal options
community.general.proxmox_kvm:
proxmox_default_behavior: 'no_defaults'
api_user: 'root@pam'
api_password: 'blahblahblah'
api_host: 'gluster-test'
name: 'test-vm'
node: 'gluster-test'
Which I then run using
ansible-playbook --ask-become-pass setup-test-vm.yml
which gives me this output:
Code:
BECOME password:
PLAY [gluster-test] *******************************************************************************************************************************************
TASK [Gathering Facts] ****************************************************************************************************************************************
ok: [gluster-test]
TASK [Create new VM with minimal options] *********************************************************************************************************************
fatal: [gluster-test]: FAILED! => {"changed": false, "msg": "authorization on proxmox cluster failed with exception: HTTPSConnectionPool(host='gluster-test.jordanbradley.site', port=8006): Max retries exceeded with url: /api2/json/access/ticket (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f2efe49b6a0>: Failed to establish a new connection: [Errno 110] Connection timed out'))"}
PLAY RECAP ****************************************************************************************************************************************************
gluster-test : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
Which is strange because if I run this playbook against my production proxmox server I get a different error.
Last edited: