Revert to snapshot, resets creation date. Intended behaviour?

[probain]

I just noticed that one VM I did a revert from snapshot on. Now that VM has that same date as its creation date. This is not really what I was expecting... Although I can somewhat se the logic/reason. It being that one could argue that it was "created" by that reverting to snapshot.. It is not indicative of when the VM itself acctually was created.

Is this intended behaviour and working as expected?

[poddingue]

From what I understand, when XCP-ng reverts to a snapshot it restores the full VM state from that point (metadata included, not just the disk contents) so the creation date field would get rolled back along with everything else; that might be why it now matches the snapshot timestamp rather than
the original. I might be wrong about the internals though.

It's a bit confusing if you were relying on that field to track VM history, and I don't think https://docs.xen-orchestra.com/xo5/manage_infrastructure#snapshot-management covers this explicitly.
Might be worth a mention to @Team-Documentation-Knowledge-Management; it's the kind of thing that catches people off guard because nothing warns you upfront that metadata rolls back too.
My $0.02.

[jr-m4]

@poddingue

Thanks for your input.
Yes I'm aware that basically everything on the VM is incorporated into the snapshot. Including settings and metadata. This is acctually why I was surprised that the creation date wasn't preserved as part of that metadata. And as you say, if one uses that metric to track VM history. Then it can, and will, throw you off.

I'll gladly submit this as a feature request. But my gut feeling is that it is more akin to a bug than missing feature per se.

Thanks!