invalid format - unable to parse volume ID 'vm-104-disk-1'

[onegreyonewhite]

2019/12/28 04:05:57 [INFO] [node-controller-docker-machine] (k8s-1) {"time":"2019-12-28T04:05:54.06368707Z","level":"INFO","prefix":"-","file":"proxmoxdriver.go","line":"60","message":"Creating VM '104' with '6144' of memory"}
2019/12/28 04:05:57 [INFO] [node-controller-docker-machine] (k8s-1) RESTY 2019/12/28 04:05:54 
2019/12/28 04:05:57 [INFO] [node-controller-docker-machine] (k8s-1) ---------------------- REQUEST LOG -----------------------
2019/12/28 04:05:57 [INFO] [node-controller-docker-machine] (k8s-1) POST  /api2/json/nodes/cloud/qemu  HTTP/1.1
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) HOST   : cloud.domain:8006
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) HEADERS:
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)              Content-Type: application/x-www-form-urlencoded
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)                    Cookie: PVEAuthCookie=PVE:user@pam:cookie
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)       Csrfpreventiontoken: token
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)                User-Agent: go-resty/1.12.0 (https://github.com/go-resty/resty)
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) BODY   :
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) agent=1&autostart=1&cdrom=local%!A(MISSING)iso%!F(MISSING)rancheros-proxmoxve-autoformat.iso&cores=4&kvm=1&memory=6144&name=k8s-1&net0=virtio%!C(MISSING)bridge%!D(MISSING)vmbr0&ostype=l26&pool=heap&scsi0=vm-104-disk-1&vmid=104
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) ----------------------------------------------------------
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) RESTY 2019/12/28 04:05:54 
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) ---------------------- RESPONSE LOG -----------------------
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) STATUS              : 400 Parameter verification failed.
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) RECEIVED AT : 2019-12-28T04:05:54.087624868Z
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) RESPONSE TIME       : 23.668001ms
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) HEADERS:
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)             Cache-Control: max-age=0
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)            Content-Length: 140
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)              Content-Type: application/json;charset=UTF-8
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)                      Date: Sat, 28 Dec 2019 04:05:54 GMT
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)                   Expires: Sat, 28 Dec 2019 04:05:54 GMT
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)                    Pragma: no-cache
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)                    Server: pve-api-daemon/3.0
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) BODY   :
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) {
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)    "errors": {
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)       "scsi0": "invalid format - format error\nscsi0.file: invalid format - unable to parse volume ID 'vm-104-disk-1'\n\n"
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)    },
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1)    "data": null
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) }
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] (k8s-1) ----------------------------------------------------------
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine] The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2019/12/28 04:05:58 [INFO] [node-controller-docker-machine]

What am I doing wrong? Used v3-pre3 release and lvm-thinpool.

[lnxbil]

That error is new, I have to create a test environment for thin-lvm.

[cperrin88]

The same happens on NFS. Local works as expected. I see that in the request there is no file extension on the image name. When provisioning on local it works. Maybe that is the problem.

(test2) Calling .Create
(test2) RESTY 2020/01/16 13:49:00
(test2) ---------------------- REQUEST LOG -----------------------
(test2) POST  /api2/json/nodes/pve/storage/NFS/content  HTTP/1.1
(test2) HOST   : 192.168.178.20:8006
(test2) HEADERS:
(test2)              Content-Type: application/x-www-form-urlencoded
(test2)                    Cookie: PVEAuthCookie=PVE:root@pam:5E205BFD::PRCAvj5DBGayGLs5cYxWeWxNZ2k3fP+/3AQL7iscIdys5g9HpEJN6ErwaKaAkhd8PXFu7q9fOWtqqmjxQOlvvQs7mnkUkgMi0nnlFi1uQJw38RNlyvalDjYO3iuVxtiuIY5YV+UequNemi1NL69DNEYReobNA82tkAz+W/6cuWxXW6QpNYxSNSHPGH3e7mrfFHpjg8/7XYPgp1hbqvcgh/eJDlcvTKPEGZPut2iEaefMb89ODP+sGjMo2dYSgQ9RaLLZoa4aE7CXdvuZQlI0bfLiGgRar38hxjKSmrxKprxO9rEMPHIqm6d0lL6RymDahNbn++x8iZsOhsH836eC+A==
(test2)       Csrfpreventiontoken: 5E205BFD:smdE5n3DD2hoSbvAWeVfEFATbaR5p2iv0mN/MfmabNk
(test2)                User-Agent: go-resty v1.7 - https://github.com/go-resty/resty
(test2) BODY   :
(test2) filename=vm-102-disk-1&size=16G&vmid=102
(test2) ----------------------------------------------------------
(test2) RESTY 2020/01/16 13:49:00
(test2) ---------------------- RESPONSE LOG -----------------------
(test2) STATUS          : 500 error with cfs lock 'storage-NFS': unable to parse volume filename 'vm-102-disk-1'
(test2) RECEIVED AT     : 2020-01-16T13:49:00.2463267+01:00
(test2) RESPONSE TIME   : 49.2477ms
(test2) HEADERS:
(test2)             Cache-Control: max-age=0
(test2)            Content-Length: 13
(test2)              Content-Type: application/json;charset=UTF-8
(test2)                      Date: Thu, 16 Jan 2020 12:50:06 GMT
(test2)                   Expires: Thu, 16 Jan 2020 12:50:06 GMT
(test2)                    Pragma: no-cache
(test2)                    Server: pve-api-daemon/3.0
(test2) BODY   :
(test2) {
(test2)    "data": null
(test2) }
(test2) ----------------------------------------------------------
Error creating machine: Error in driver during machine creation: status code was '500' and error is
500 error with cfs lock 'storage-NFS': unable to parse volume filename 'vm-102-disk-1'
notifying bugsnag: [Error creating machine: Error in driver during machine creation: status code was '500' and error is
500 error with cfs lock 'storage-NFS': unable to parse volume filename 'vm-102-disk-1']

[Psayker]

Resolve this issue, in pull request

[bgulla]

Resolve this issue, in pull request

I want to test this but go get github.com/vstconsulting/docker-machine-driver-proxmox-ve isnt producing a binary for me, can you help?

[Psayker]

@bgulla I add binary to pull request. I try go get github.com/vstconsulting/docker-machine-driver-proxmox-ve and successfully load package, try add flag -v for more information

[lnxbil]

New version with a lot of fixes and merged PR. Please try again and report back.

[onegreyonewhite]

New version with a lot of fixes and merged PR. Please try again and report back.

I would like to, but Rancher now report an error on creating a Node Template:

{" baseType ":" error "," code ":" MissingRequired "," message ":" a Config field must be set "," status ": 422," type ":" error "}

and I didnt know how to fix it...

But it worked with #24. May be problem with naming of driver and args.

[lnxbil]

I'd like to reproduce the errors you got with the Rancher setup, how can I have such a setup? Can someone point me to a setup guide so that I can try to replicate the issue myself?

[onegreyonewhite]

• Single node installation.
• Adding Custom Node Drivers.

[taniahagan]

Hi,

Hope you don't mind commenting on this thread. I also seem to be receiving the same error, I am currently running: Foreman : 2.0.0-rc2 Proxmox: tfm-rubygem-fog-proxmox.noarch 0.10.0-1.el7

Initially for a few new hosts it worked, now I see the following: E|app|fdd8efac] Failed to save: Failed to create a compute Proxmox- (Proxmox) instance : Expected([200]) <=> Actual(400 Bad Request) excon.error.response :body => "{"errors":{"ide2":"invalid format - format error\nide2.file: invalid format - unable to parse volume ID 'image'\n\n"},"data":null}" :cookies => [ ] :headers => { "Cache-Control" => "max-age=0" "Connection" => "close" "Content-Length" => "130" "Content-Type" => "application/json;charset=UTF-8" "Date" => "Fri, 20 Mar 2020 14:56:00 GMT" "Expires" => "Fri, 20 Mar 2020 14:56:00 GMT" "Pragma" => "no-cache" "Server" => "pve-api-daemon/3.0" } :host => "" :local_address => "" :local_port => 42644 :path => "/api2/json/nodes//qemu" :port => 8006 :reason_phrase => "Parameter verification failed." :remote_ip => "" :status => 400 :status_line => "HTTP/1.1 400 Parameter verification failed.\r\n"

If i can help provide any more logs to help resolve, please let me know. I'd love to resolve this issue as soon as possible.

Thanks, Tania

[lnxbil]

Could you try to replicate with v4?