From 27c91eee95954a2998cd3120d6bfde905c462de2 Mon Sep 17 00:00:00 2001 From: twothatit Date: Sun, 8 Feb 2026 22:23:52 +0100 Subject: [PATCH] Fix deploy crash: use valid log status 'info' instead of 'warning' The deployment_logs table has a CHECK constraint allowing only 'success', 'error', 'info'. Using 'warning' caused an IntegrityError that crashed the entire deployment. Co-Authored-By: Claude Opus 4.6 --- app/services/netbird_service.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/services/netbird_service.py b/app/services/netbird_service.py index ef73248..1a38e44 100644 --- a/app/services/netbird_service.py +++ b/app/services/netbird_service.py @@ -319,7 +319,7 @@ async def deploy_customer(db: Session, customer_id: int) -> dict[str, Any]: ssl_ok = npm_result.get("ssl", False) if not npm_result.get("error") else False if not ssl_ok: _log_action( - db, customer_id, "deploy", "warning", + db, customer_id, "deploy", "info", "SSL certificate not created automatically. " "Please create it manually in NPM or ensure DNS resolves and port 80 is reachable, then re-deploy.", )