Symptom

Deployments were failing with the following logs on pigtail: NGUI: 04-03 20:23:31 INFO [DeploymentRunner] okhttp3.internal.Platform.log <-- END HTTP (23095-byte body) NGUI: 04-03 20:23:31 DeploymentRunner: ERROR NormalDeploymentController:146 - Deployment could not successfully initialize due to validation failures. NGUI: 04-03 20:23:31 DeploymentRunner: ERROR DeploymentRunner:230 - DeploymentException occurred while executing deployment request : 64396e0d-d25d-11ed-bfa4-1f5184160d6e NGUI: 04-03 20:23:31 DeploymentException: You cannot disable regeneration deployment mode. There was a deployment failure, and the system must perform a successful full deployment (forceRefreshDeploymentData=true) before partial deployments are possible again. NGUI: 04-03 20:23:31 DeploymentRunner: ERROR DeploymentRunner:231 - DeploymentException: You cannot disable regeneration deployment mode. There was a deployment failure, and the system must perform a successful full deployment (forceRefreshDeploymentData=true) before partial deployments are possible again. After applying WA from bug CSCvt22254 "touch /ngfw/var/cisco/deploy/pkg/var/cisco/packages/vdb-.tgz" the following error was appearing on pigtail: NGUI: 04-03 20:36:58 DeploymentRunner: ERROR NormalDeploymentController:168 - Failed to complete deployment: java.util.concurrent.ExecutionException: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT OR REPLACE INTO DEPLOYING_policies (uuid, last_changed, name, description, type, data, modified, md5sum, authority) SELECT uuid, last_changed, name, description, type, data, modified, md5sum, authority FROM DEPLOYED_policies WHERE uuid = ?]; SQL state [null]; error code [1]; [SQLITE_ERROR] SQL error or missing database (no such table: DEPLOYED_policies); nested exception is org.sqlite.SQLiteException: [SQLITE_ERROR] SQL error or missing database (no such table: DEPLOYED_policies) NGUI: 04-03 20:36:58 DeploymentRunner: INFO NormalDeploymentController:174 - Posted event to revert back the event rate after deploy through NGFWEventBus NGUI: 04-03 20:36:58 eventbus-service-4: INFO SensorEventManager:122 - com.cisco.sensor.event.engine.SensorEventManager NGUI: 04-03 20:36:58 eventbus-service-4: INFO SensorEventManager:125 - com.cisco.sensor.event.engine.SensorEventManager NGUI: 04-03 20:36:58 DeploymentRunner: ERROR DeploymentRunner:230 - DeploymentException occurred while executing deployment request : 133b8fcd-d25f-11ed-bfa4-bdb78ef3450e NGUI: 04-03 20:36:58 DeploymentException:java.util.concurrent.ExecutionException: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT OR REPLACE INTO DEPLOYING_policies (uuid, last_changed, name, description, type, data, modified, md5sum, authority) SELECT uuid, last_changed, name, description, type, data, modified, md5sum, authority FROM DEPLOYED_policies WHERE uuid = ?]; SQL state [null]; error code [1]; [SQLITE_ERROR] SQL error or missing database (no such table: DEPLOYED_policies); nested exception is org.sqlite.SQLiteException: [SQLITE_ERROR] SQL error or missing database (no such table: DEPLOYED_policies) NGUI: 04-03 20:36:58 DeploymentRunner: ERROR DeploymentRunner:231 - DeploymentException:java.util.concurrent.ExecutionException: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT OR REPLACE INTO DEPLOYING_policies (uuid, last_changed, name, description, type, data, modified, md5sum, authority) SELECT uuid, last_changed, name, description, type, data, modified, md5sum, authority FROM DEPLOYED_policies WHERE uuid = ?]; SQL state [null]; error code [1]; [SQLITE_ERROR] SQL error or missing database (no such table: DEPLOYED_policies); nested exception is org.sqlite.SQLiteException: [SQLITE_ERROR] SQL error or missing database (no such table: DEPLOYED_policies)

Conditions

FPR-1010 (FDM Managed) Version: 7.2.0.1 (Build 12) / 9.18(1)200 VDB 361 SRU to Rule Update 2023-04-03-001 Snort2, version 2.9.20-108

Workaround

Open a TAC case for the workaround

Further Problem Description