Kadin Sayani
Kadin Sayani
Hi, I'd like to tackle this issue. If possible, can you please provide steps to reproduce some of these errors?
It appears that the snapshot expiry date is correct, hence why LXD is aware of the snapshot (see below snippet). However, `lxd recover` is using the volume_snapshots expiry which is...
@tomponline would this be a good exercise for me to do as part of my upcoming work improving live migration of VMs between different CPU architectures?
> In the above, it's listing image volumes (fingerprint) along with instances and image aliases. Is the output of `lxc storage volume list default` also erroneous? It makes sense for...
I don't see any logic in my change that would cause a regression for the `lxc storage volume copy` tab completion. If the completion is showing results containing storage volumes...
> It seems only custom volumes are copy'able by lxc storage volume copy so the tab completion should only offer those. Gotcha, thanks for clarifying! > Odd as I don't...
I just tested a fresh install of the LXD snap on a fresh VM and I'm observing the extraneous space after tab completing `lxc storage volume copy`. After regenerating the...
Added similar completion logic to `lxc storage volume move` as well.
Reopening to track the extraneous space issue.
I believe I've found the problem causing the extraneous space to be added after running `lxc storage volume copy [TAB]`. snapd intercepts all shell completion requests. Given that the default...