Now that I'm starting to test XCP-ng 8.2 in my environment, I'm starting to use XO a lot more as part of my testing and noticed an odd thing with snapshots created by XO.
Snapshots created by XO are showing up in the "All VMs" list in xsconsole as though they are VMs which haven't been started while VM snapshots created by other means such as XenCenter, XCP-ng Center, and xe CLI vm-snapshot commands don't. The snapshots created by XO are also showing up in the xe vm-list output while the others don't; I suspect this list is what xsconsole is fetching for its "All VMs" list.
I've compared parameters for the snapshots created by all three methods and the only thing that stands out is that the visible vs. invisible snapshots have different is-a-template parameters. CLI and XCP-ng Center snapshots have both is-a-snapshot and is-a-template set to true while XO snapshots have is-a-snapshot set to true and is-a-template set to false.
I've tested this with both a recent XOA and XO built from source and see the same problem with both. It also doesn't seem to matter which version of XCP-ng or XenServer I'm running it on; I've seen exactly the same problem with both XCP-ng 8.2 and XenServer 7.1.
Have I found a bug or is this expected, normal operation for XO?