When the openshell StatefulSet is restarted (e.g., via kubectl rollout restart), the new pod sometimes starts with the SQLite database in a locked state. All subsequent ListSandboxes calls fail with:
```
database error: error returned from database: (code: 5) database is locked
```
The only recovery path we found is deleting the pod and the PVC (openshell-data-openshell-0), which forces a fresh database on next pod start.
Reproduction
- Run
kubectl rollout restart statefulset/openshell -n openshell
- After the new pod is Running, call
ListSandboxes — observe the database is locked 500 error
Expected behavior
The database should be accessible after pod restart without requiring PVC deletion.
Environment
- Kubernetes StatefulSet with
directpv-hdd StorageClass
- SQLite embedded in openshell-gateway
When the
openshellStatefulSet is restarted (e.g., viakubectl rollout restart), the new pod sometimes starts with the SQLite database in a locked state. All subsequentListSandboxescalls fail with:```
database error: error returned from database: (code: 5) database is locked
```
The only recovery path we found is deleting the pod and the PVC (
openshell-data-openshell-0), which forces a fresh database on next pod start.Reproduction
kubectl rollout restart statefulset/openshell -n openshellListSandboxes— observe thedatabase is locked500 errorExpected behavior
The database should be accessible after pod restart without requiring PVC deletion.
Environment
directpv-hddStorageClass