[Bug] Unable to remove Snapshot Replication show error Replica teardown failed — replication job kept

[nimitnga]

Hey there! 👋 Thanks for taking the time to report this bug — we appreciate it!

Please keep in mind: PegaProx is developed and maintained entirely by volunteers in our free time. We do our best, but we can't work magic 🪄 — please be patient, we'll get to your issue as soon as we can.

Want to help keep PegaProx alive?

• ⭐ Star the project — it's free and helps a lot!
• 💖 Become a Sponsor — helps us dedicate more time to development
• 🤝 Contributing code or docs is always welcome too!

---

Describe the bug

Hi There,

Cannot delete Snapshot Replication job. PegaProx v.0.9.13.1 running on Proxmox VM OS Debian 13.5, Please advise.

Steps to Reproduce

1. Create Snapshot Replication job.
2. Manual run Replication job successfully.
3. Delete Snapshot Replication job not complete -> Error "Replica teardown failed — replication job kept".

Expected behavior

Environment

• PegaProx Version: PegaProx Beta 0.9.13.1
• Installation Method: Install script deploy.sh
• OS: DEBIAN_VERSION_FULL=13.5
• Browser: google chrome Version 149.0.7827.104 (Official Build) (64-bit).
• Behind Reverse Proxy? No.
• UI? Modern Layout

Logs

Screenshots

Checklist

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

[mkellermann97]

Thanks for the clear repro — pinned it. Two things are happening: PegaProx refused to tear down the replica because it couldn't prove that VM is this job's replica (a deliberate safety guard, so it never nukes a bystander), and the delete dialog then kept the whole job instead of letting you drop it — that "keep" choice wasn't actually overriding the job's stored "remove target" flag, so you got wedged. Fixed on Testing: choosing "keep the replica" now reliably drops the job and leaves the replica alone; it'll be in the next build. On your current 0.9.13.1 the clean workaround is to delete that replica VM yourself in Proxmox first, then delete the job in PegaProx — with the replica gone there's nothing to tear down and the job removes cleanly. If you can grab the exact server log line ([XCREPL] Job ... replica teardown failed: ...) I'll confirm the replica-naming side too.

If PegaProx saves you time, a tip at opencollective.com/pegaprox keeps it moving. — Marcus