returned diskname is not correct

[Selleslagh Tom]

Hello,

I try to use your driver (v2) as a node-driver in Rancher to provide a Kubernetes cluster.
But i have a issue, the logs return me this error :
Error creating machine: Error in driver during machine creation: returned diskname is not correct.

However, as you can see in the screen shot, the disk is correctly created but the VM isn't created:

Here is my proxmox node template in Rancher:

Any idea to resolve this problem?

[Andreas Steinel]

Hi and thank you for using the driver with kubernetes! It's still on my todo list :-D

I recently introduced a check that should try to detect any errors with the disk creation, so that is to blame for that. Unfortunately, it sends it's expected and actual data in the second line of the error message, that is not displayed in your output (maybe the software expects only one line of error).

Anyway, I have a possible workaround but no machine I can actually test it. Would you be so kind?

https://github.com/lnxbil/docker-machine-driver-proxmox-ve/releases/tag/possible-fix-for-16

[Selleslagh Tom]

I can be the tester ;)

So, i have just tested your proposed release but that don't resolve the issue.
However i have new informations from the logs:

I hope it help you more.

[Andreas Steinel]

Thank you, now with a better error message I can deal with. brb

[Andreas Steinel]

So, another prerelease

[Selleslagh Tom]

We are going forward.

The VM is correctly deploy with rancherOS.
However I have a new error :

I think it's a other issue and I don't know if that come from the driver. What do you think about this error?

a possible way : the name of the driver don't match...

[Andreas Steinel]

Yes, this is a new and external error. Strange that it is found in the first place to create the VM. In which directory did you copy the driver file?

[Selleslagh Tom]

It think i have a possible solution :
change proxmox to proxmoxve into the main.go ... i think it can do the job

[Selleslagh Tom]

Yes, this is a new and external error. Strange that it is found in the first place to create the VM. In which directory did you copy the driver file?

In rancher you upload the driver from the interface... and then he store it somewhere...
but i try a fork of you repo where the import name was proxmoxve and i don't have this issue.

I think it's important to work on your repo because it is pointed by rancher.

[Andreas Steinel]

Just to be clear, changing this works?

diff --git a/cmd/docker-machine-driver-proxmox-ve/main.go b/cmd/docker-machine-driver-proxmox-ve/main.go
index 5ca2279..7a2df1f 100644
--- a/cmd/docker-machine-driver-proxmox-ve/main.go
+++ b/cmd/docker-machine-driver-proxmox-ve/main.go
@@ -2,9 +2,9 @@ package main
 
 import (
        "github.com/docker/machine/libmachine/drivers/plugin"
-       proxmox "github.com/lnxbil/docker-machine-driver-proxmox-ve"
+       proxmoxve "github.com/lnxbil/docker-machine-driver-proxmox-ve"
 )
 
 func main() {
-       plugin.RegisterDriver(proxmox.NewDriver("default", ""))
+       plugin.RegisterDriver(proxmoxve.NewDriver("default", ""))
 }

[Andreas Steinel]

Ah, nevermind. Found your fork.

[Andreas Steinel]

So, changed it in 5014644 and forgot to reference this issue.

[Andreas Steinel]

I've not uploaded a new release yet, you're capable of building your own as you revealed above :-D

[Selleslagh Tom]

i encourage you to build and create the pre-release 3... to avoid problem with our possible different golang version

[Andreas Steinel]

i encourage you to build and create the pre-release 3... to avoid problem with our possible different golang version

Sure thing ... online.