mirror of
https://github.com/retspen/webvirtcloud
synced 2026-11-08 11:16:47 +00:00
addc7ccfcb
Two computes decide the owners of the same UUID: the one the VM left buries them in a tombstone (or a compute delete does), the one it went to restores them. On PostgreSQL the two ran at once: the restore still saw the old row of the uncommitted bury, skipped, and the VM ended up without owners while the tombstone stayed. SQLite was never affected: its IMMEDIATE transactions take the write lock at the start. The reconcile and the compute delete now take one transaction-level advisory lock (pg_advisory_xact_lock) when their database step starts, so ownership decisions run one after another on PostgreSQL as they do on SQLite. Reading libvirt stays outside the lock. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_api_security.py | ||
| test_audit_rows.py | ||
| test_compute_password.py | ||
| test_cpu_graph.py | ||
| test_migration_address.py | ||
| test_operation_locks.py | ||
| test_overview_status.py | ||
| test_ownership.py | ||
| test_ownership_race.py | ||
| test_quota_down_host.py | ||
| test_reconciliation.py | ||
| test_validators.py | ||
| test_views.py | ||