lehn-etracker / vagrant-proxmox Goto Github PK

I have a Proxmox-Server that is using a valid let's encrypt certificate.

When trying to connect using vagrant-proxmox i often get the above mentioned error on the first try.

Trying again immediately afterwards is successful.

I'm currently unable to create my virtual machines and only get this error:

   ==> default: Trying to adjust forwarded_port params
   Unable to communicate with proxmox server:
   
   Unable to establish an ssh connection to the virtual machine...

I think, there is something wrong with my network config, but i have no details.

Proxmox allows to install SSH public keys during LXC creation.

My proxmox cluster is on an internal network. Would it be possible to disable the SSL cert verification via an optional parameter for the proxmox provider endpoint?
proxmox.verify_ssl = false could then be translated to :verify_ssl => false for the RestClient calls.

Log output:

$ RESTCLIENT_LOG=stdout vagrant up --provider proxmox
RestClient.post "https://proxmox:8006/api2/json/access/ticket", "username=vagrant&password=password", "Accept"=>"*/*", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"41", "Content-Type"=>"application/x-www-form-urlencoded", "User-Agent"=>"rest-client/2.0.2 (linux-gnu x86_64) ruby/2.7.1p83"
Unable to communicate with proxmox server:

ConnectProxmox: SSL_connect returned=1 errno=0 state=error: certificate verify failed (unable to get local issuer certificate)

Imagine, your using test-kitchen with vagrant and vagrant-proxmox and kitchen-nodes. When you've to setup three nodes, each within the same subnet, vlan, etc. It would be much cleaner if we could write common setting only once.

If you currently override parts of driver > network section of one suite (node) in .kitchen.yml you will loose all commonly defined ones.