Skip to content

Fix some dependent volume issues - #4137

Merged
presztak merged 7 commits into
lxc:mainfrom
stgraber:storage
Oct 9, 2026
Merged

presztak merged 7 commits into
lxc:mainfrom
stgraber:storage

Conversation

@stgraber

@stgraber stgraber commented Oct 8, 2026

Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
When copying an instance from one of its snapshots, the dependent
volumes were copied from their current state. Use the volume snapshot
matching the instance snapshot instead, in both the same-pool and the
cross-pool paths. The latter also needed its dependent volume transfer
enabled for snapshot sources, which crashed on the missing instance
section of the snapshot's config.

Closes lxc#4125

Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
A refresh request carries the source's devices, so the dependent
volume check refused it unless the overrides were passed again.

Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
The snapshot records of a copy kept the source's dependent volume
names, so restoring them touched the source's volumes and refreshes
failed validation.

Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
The refresh update is built from the source, which re-pointed the
dependent devices at the source's volumes and dropped a root disk
device the target got from --storage.

Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
@stgraber
stgraber requested a review from presztak October 8, 2026 15:26
@presztak
presztak merged commit 16e9577 into lxc:main Oct 9, 2026
96 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants