[Bug] ESXi snapshot creation not visible in PegaProx UI

[VodaAKY]

Describe the bug

After creating a snapshot through PegaProx on a VM on ESXi 8, the PegaProx UI reports 0 snapshots.
The snapshot is created and visible in the ESXi UI.

Steps to Reproduce

1. Create snapshot on ESXi VM in PegaProx UI
2. PegaProx successfully creates snapshot
3. Reload browser does not reflect the new snapshot

Expected behavior

PegaProx UI should update automatically after successful snapshot creation.

Environment

• PegaProx Version: 0.9.9.3
• Installation Method: Deploy script
• OS: Ubuntu 26.04
• • Browser: Chrome 147
• Behind Reverse Proxy? No
• UI? Modern Layout

Logs

Screenshots

Checklist

• [x ] I have searched existing issues to make sure this is not a duplicate
• [x ] I am using the latest version of PegaProx

[gyptazy]

Hey @VodaAKY.

the snapshot management overview scope of this is not meant for VMware based systems and only available for Proxmox based ones.

Cheers,
gyptazy

[VodaAKY]

Hi @gyptazy

It makes no sense to me that the snapshot tab is there at all for ESXi, then. It is misleading, at best.
As I understand it, It is a critical parameter for a successful migration whether or not a snapshot is present, or am I mistaken?

[gyptazy]

Hey @VodaAKY,

It makes no sense to me that the snapshot tab is there at all for ESXi, then. It is misleading, at best. As I understand it, It is a critical parameter for a successful migration whether or not a snapshot is present, or am I mistaken?

This is basically the UI integration of ProxSnap (https://github.com/gyptazy/ProxSnap) for PegaProx which is meant for Proxmox VE based systems. ProxSnap does not have any support for ESXi systems.

To not create any further confusions, I'll add a PR that will not show this tab in a context of a VMware / ESXi based system.

Cheers,
gyptayz

[VodaAKY]

How come the "Create Snapshot" is working then?

[mkellermann97]

Hi @VodaAKY, fixed in v0.9.10. pyVmomi sometimes returns a stale .snapshot tree right after CreateSnapshot_Task completes (we saw it consistently on ESXi 8.x). Added a short retry loop in pegaprox/core/vmware.py that re-fetches the snapshot tree until the new id shows up, with a sane upper bound so we don't spin forever on a real failure. UI now reflects new snapshots immediately.

Closing — please reopen if it still happens on v0.9.10+.

— MK