fix(host): clear pooled SQLite handles before renaming the imported inbound-key file — Windows refused the rename, so the import re-ran every boot (QA vq03/vq04 2026-10-22)

2026-10-22 15:56:00 -04:00
parent 5ad6f83176
commit 6ed6800b84
3 changed files with 61 additions and 0 deletions
@@ -71,6 +71,12 @@ about this at boot). To move an existing pair over:
 5. Check the import log line on each node (`grep -i "api-key store import\|zbauth"` in the
   node's log) — one node reports the keys it inserted, the other reports the ones it found
   already present (skipped); together they cover the union of both nodes' prior SQLite files.
+   On a **Windows** central running a build before 2026-10-22 the import succeeds but the
+   `*.imported` rename then fails with `IOException: … being used by another process` (the
+   importer's pooled SQLite handle; fixed by clearing the pools before the rename) — the import
+   re-runs harmlessly on every boot. Fix it by hand: stop that node's Central, wait for its
+   `ZB.MOM.WW.ScadaBridge.Host` process to exit, rename `inbound-api-keys.sqlite` and its
+   `-wal`/`-shm` siblings to `*.imported`, start it again (QA, 2026-10-22).
 6. Run `security api-key list` against each node's management endpoint and confirm both show
   the same keys.
 7. After a quarantine period (once you're confident the import is correct and no rollback is