Unsupported format "qcow2"

[prologic]

Trying out latest commits:

$ docker-machine create -d proxmox-ve --proxmox-storage zfs --proxmox-node vz1 --proxmox-memory-gb 1 --proxmox-image-file rancheros.iso --proxmox-host vz1 --proxmox-password $(read -s -p 'Password: ' password; echo $password) test1
Password: Running pre-create checks...
Creating machine...
(test1) {"time":"2018-04-17T22:56:11.14660046-07:00","level":"WARN","prefix":"-","file":"log.go","line":"297","message":"Create called"}
(test1) {"time":"2018-04-17T22:56:11.146728495-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Connecting to vz1 as root@pam with password 'xxx'\n"}
(test1) {"time":"2018-04-17T22:56:11.247815209-07:00","level":"WARN","prefix":"-","file":"log.go","line":"297","message":"Connected to version '5.1'"}
(test1) {"time":"2018-04-17T22:56:11.24785578-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Retrieving next ID\n"}
(test1) {"time":"2018-04-17T22:56:11.251795712-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Next ID was '105'\n"}
(test1) {"time":"2018-04-17T22:56:11.251851533-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Creating disk volume 'vm-105-disk-1.qcow2' with size '16G'\n"}
(test1) {"time":"2018-04-17T22:56:11.276793424-07:00","level":"FATAL","prefix":"-","file":"log.go","line":"321","message":"status code was '500' and error is\n500 unsupported format 'qcow2' at /usr/share/perl5/PVE/Storage/ZFSPoolPlugin.pm line 229."}
Error creating machine: Error in driver during machine creation: unexpected EOF

[prologic]

Unclear to me what this error really means:

500 unsupported format 'qcow2' at /usr/share/perl5/PVE/Storage/ZFSPoolPlugin.pm line 229

I'm running Proxmox VE 5.1-42

[prologic]

The only other supported option is raw but it fails with a 400 Bad Request

$ docker-machine create -d proxmox-ve --proxmox-storage zfs --proxmox-storage-type raw --proxmox-node vz1 --proxmox-memory-gb 1 --proxmox-image-file rancheros.iso --proxmox-host vz1 --proxmox-password $(read -s -p 'Password: ' password; echo $password) test1
Password: Running pre-create checks...
Creating machine...
(test1) {"time":"2018-04-17T23:03:16.903869124-07:00","level":"WARN","prefix":"-","file":"log.go","line":"297","message":"Create called"}
(test1) {"time":"2018-04-17T23:03:16.904033189-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Connecting to vz1 as root@pam with password 'xxx'\n"}
(test1) {"time":"2018-04-17T23:03:16.954658718-07:00","level":"WARN","prefix":"-","file":"log.go","line":"297","message":"Connected to version '5.1'"}
(test1) {"time":"2018-04-17T23:03:16.954704469-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Retrieving next ID\n"}
(test1) {"time":"2018-04-17T23:03:16.95858531-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Next ID was '105'\n"}
(test1) {"time":"2018-04-17T23:03:16.958627283-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Creating disk volume 'vm-105-disk-1' with size '16G'\n"}
(test1) {"time":"2018-04-17T23:03:17.069508333-07:00","level":"WARN","prefix":"-","file":"log.go","line":"301","message":"Creating VM '105' with '1024' of memory\n"}
(test1) {"time":"2018-04-17T23:03:17.11822187-07:00","level":"FATAL","prefix":"-","file":"log.go","line":"321","message":"status code was '400' and error is\n400 Parameter verification failed."}
Error creating machine: Error in driver during machine creation: unexpected EOF

[lnxbil]

Yes, if something fails, we have - at the moment - no better error message. We need to check if every parameter is right before using them, because the API is not very descriptive in case of an error. We also need to strip empty parameters from the request before sending and I assume the error comes from an empty pool parameter.

Best is also to check /var/log/pveproxy/access.log on the server to get the actual request data and see if some parameter is empty, the API (i assume) cannot handle empty variables, only if they are not present.

[prologic]

Out of interest; Are you also running Proxmox VE 5.1-42?

James Mills / prologic

E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

On Tue, Apr 17, 2018 at 11:15 PM, Andreas Steinel notifications@github.com wrote:

Yes, if something fails, we have - at the moment - no better error message. We need to check if every parameter is right before using them, because the API is not very descriptive in case of an error. We also need to strip empty parameters from the request before sending and I assume the error comes from an empty pool parameter.

Best is also to check /var/log/pveproxy/access.log on the server to get the actual request data and see if some parameter is empty, the API (i assume) cannot handle empty variables, only if they are not present.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lnxbil/docker-machine-driver-proxmox-ve/issues/4#issuecomment-382274639, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOv-gwpKv-JGnQ6hnA0VLfLbZo479rtks5tptoAgaJpZM4TZdsI .

[lnxbil]

Out of interest; Are you also running Proxmox VE 5.1-42?

Tested it against 5.1-35 and 4.4-18.

[lnxbil]

So, I added some debug flags to be able to see what's happening in the driver and on the wire (with resty debugging). So, please check again.

[prologic]

Wil do!

James Mills / prologic

E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

On Wed, Apr 18, 2018 at 2:44 PM, Andreas Steinel notifications@github.com wrote:

So, I added some debug flags to be able to see what's happening in the driver and on the wire (with resty debugging). So, please check again.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lnxbil/docker-machine-driver-proxmox-ve/issues/4#issuecomment-382539341, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOv-pD8JCEVwUJpA3_lU7ED1P5ACr4Sks5tp7PNgaJpZM4TZdsI .

[lnxbil]

Any news on this?