Walter Doekes

^- PR

Because we have a load balancer, on a normal port, with a valid certificate, in front of our proxmoxen. If the example had shown an RFC1918 IP, I would've used...

Apparently you're ending up here: https://github.com/ossobv/proxmove/blob/6935ecffa702e7b88e2989a9acd50f813b411071/proxmove#L913-L927 And then here: https://github.com/ossobv/proxmove/blob/6935ecffa702e7b88e2989a9acd50f813b411071/proxmove#L895-L909 Which should be: ``` 2022-05-22 07:27:27,138: DEBUG: (exec) ssh [email protected] ls -l /dev/pve/vm-103-disk-0 ``` Which results in: ``` lrwxrwxrwx 1...

Well. Then it looks like you're either in the need for this: https://github.com/ossobv/proxmove/issues/33 or this: https://github.com/ossobv/proxmove/issues/27 which are both marked as Wontfix, as I use neither. I'm sorry. I don't...

I have no idea what linked clones are. But I would say that your storage config is wrong. ``` ./proxmove overlords cluster2 pve data abtest.xxxxx.de --no-verify-ssl ``` proxmove tries to...

Ok. I guess that looks legit then :) In that case the `base-9000-disk-0/vm-123-disk-0` disk location is unexpected. ZFS has a `data/vm-123-disk-0`, but proxmove apparently gets `base-9000-disk-0/vm-123-disk-0`. ```python def get_volumes(self): if...

So, `cannot receive: local origin for clone data/vm-102-scsi0@proxmove-200507-151721 does not exist` then. I suspect it _might_ work if you get that `data/base-9000-disk-0` copied first. It should have a snapshot already...

Ok. This is not something I'm willing to spend time on. Nobody I know uses linked clones. I'll leave it open with a wontfix label for now.

@engelant: will you be working on this?

I understand :+1: