Closed bazaah closed 1 year ago
Confirmed reproducer.
I guess this is a documentation issue then.
I don't specifically need this feature, as I can (and have) do just fine with faking LXD out via lxc storage volume create ...
+ rbd clone ...
+ rbd rename ...
, swapping the underlying volume out from under LXD.
No its a bug. As it works when doing between storage pools on same server.
It seems the entire infrastructure for copying custom volume snapshots to a remote server is missing from the migration layer. So its not a small fix.
Required information
Arch Linux
lxc info
``` config:Coping from a volume snapshot does not work
I am attempting to copy a volume snapshot to another LXD instance, using the schema provided by the CLI:
Specially:
lxc storage volume copy $A:$pool/$volume/snap0 $B:$pool/$volume
This fails because it attempts to hit an endpoint that doesn't exist (or, isn't documented at any rate):
See https://linuxcontainers.org/lxd/docs/master/api/#/storage, search
storage-pools/{name}/volumes/{type}/{volume}
and note the lack of a/{snapshot}
endpoint.Steps to reproduce
lxc storage volume copy $A:$pool/$volume/snap0 $B:$pool/$volume
Information to attach
--debug output of copy attempt
``` ❯ lxc storage volume copy $A:$pool/$volume/snap0 $B:$pool/$volume DEBUG [2022-11-12T16:13:59Z] Connecting to a remote LXD over HTTPS DEBUG [2022-11-12T16:13:59Z] Sending request to LXD etag= method=GET url="https://$A/1.0" DEBUG [2022-11-12T16:13:59Z] Got response struct from LXD DEBUG [2022-11-12T16:13:59Z] { "config": "