From: Mira Limbeck <m.limbeck@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 qemu-server] fix #4201: delete cloud-init disk on rollback
Date: Fri, 11 Nov 2022 16:24:15 +0100 [thread overview]
Message-ID: <6a75c10d-1052-7fc2-88bf-27d40b301c8c@proxmox.com> (raw)
In-Reply-To: <e37c320a-c789-6ee3-78ac-6100665d63aa@proxmox.com>
On 11/11/22 16:18, Stefan Hanreich wrote:
> Test Setup:
> I created a new VM, without any Cloud-Init drive, and immediately
> created a snapshot. Then I setup a Cloud-Init drive according to the
> PVE documentation via CLI. I created another snapshot of this state
> with a Cloud-Init drive.
>
> What I tested:
> - Rolling back to the older snapshot without Cloud-Init drive, it got
> successfully removed.
> - Rolling back to the newer snapshot that includes a Cloud-Init drive,
> it successfully showed up afterwards.
>
> I also tested both of those cases with Cloud-Init drives created from
> the Web UI, in case there are any differences.
>
> Some additional tests including normal CD-ROM drives I did as well -
> just in case:
> - Rolled back from a snapshot with only a Cloud-Init drive to a
> snapshot that contains only a CD-ROM drive, the CD-ROM drive showed up
> afterwards and removed the Cloud-Init drive successfully
> - Rolled back from a snapshot with only a CD-ROM drive to a state that
> contains only a Cloud-Init drive, the Cloud-Init drive showed up
> afterwards and removed the CD-ROM drive successfully
>
>
> Code LGTM
>
>
> Reviewed-by: Stefan Hanreich <s.hanreich@proxmox.com>
> Tested-by: Stefan Hanreich <s.hanreich@proxmox.com>
>
Thanks for testing! Since it requires a rebase, I'll send a rebased v3
with your R-b and T-b tags.
prev parent reply other threads:[~2022-11-11 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:22 Mira Limbeck
2022-11-11 15:18 ` Stefan Hanreich
2022-11-11 15:24 ` Mira Limbeck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a75c10d-1052-7fc2-88bf-27d40b301c8c@proxmox.com \
--to=m.limbeck@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox