You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output of "snap list --all lxd core20 core22 core24 snapd"
lxd 6.3-d704dcb 32918 6/stable canonical** -
Output of "lxc info" or system info if it fails
.
Issue description
When restoring an instance snapshot, the description of the instance is reset to empty string. This seems like a bug. From the research below, I think the description should be not changed on snapshot restore.
For storage volumes, the description is unchanged on restoring an older snapshot. Which seems okay.
On instance snapshots, the profiles applied to the instance are not part of the snapshot and not restored either. They are kept as is after the restore process. This seems okay.
Steps to reproduce
lxc launch ubuntu:24.04 precise-ray
lxc config edit precise-ray (set a description)
lxc config show precise-ray (show the description)
lxc info precise-ray (show snapshots)
lxc snapshot precise-ray (create a snapshot)
lxc restore precise-ray snap0 (restore snapshot)
lxc info precise-ray (description is reset to empty string)
The text was updated successfully, but these errors were encountered:
Distribution
snap
Distribution version
6/stable
Output of "snap list --all lxd core20 core22 core24 snapd"
lxd 6.3-d704dcb 32918 6/stable canonical** -
Output of "lxc info" or system info if it fails
.
Issue description
When restoring an instance snapshot, the description of the instance is reset to empty string. This seems like a bug. From the research below, I think the description should be not changed on snapshot restore.
For storage volumes, the description is unchanged on restoring an older snapshot. Which seems okay.
On instance snapshots, the profiles applied to the instance are not part of the snapshot and not restored either. They are kept as is after the restore process. This seems okay.
Steps to reproduce
The text was updated successfully, but these errors were encountered: