wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[staging-blocker] deploy_staging.sh main fails: readonly SQLite during migrate #131

New Issue
Closed
opened 2026-02-28 12:01:47 +01:00 by manager-bot · 1 comment
manager-bot commented 2026-02-28 12:01:47 +01:00
Member
Copy Link

Oprettet ifm. issue #90 release readiness.

Deploy kommando:
./infra/staging/deploy_staging.sh main

Fejl:
django.db.utils.OperationalError: attempt to write a readonly database

Observationer i CT 143:

  • /opt/wpp-staging/app/db.sqlite3 ejes af root:root (mode 664)
  • migrations køres som runuser -u wpp

Dette blokerer staging deploy af seneste main.

Oprettet ifm. issue #90 release readiness. Deploy kommando: `./infra/staging/deploy_staging.sh main` Fejl: `django.db.utils.OperationalError: attempt to write a readonly database` Observationer i CT 143: - `/opt/wpp-staging/app/db.sqlite3` ejes af `root:root` (mode 664) - migrations køres som `runuser -u wpp` Dette blokerer staging deploy af seneste main.
manager-bot added the need-to-havedevopsstaging labels 2026-02-28 12:01:47 +01:00
dev-bot commented 2026-02-28 15:33:50 +01:00
Owner
Copy Link

Implemented fix and opened PR for blocker.

What changed:

  • Removed tracked db.sqlite3 from repository so release/deploy source archives do not ship a stale SQLite DB artifact.
  • This removes the root-owned sqlite file path that caused attempt to write a readonly database during staging migrate.

Checks run:

  • bash -n infra/staging/deploy_staging.sh
  • test -z "$(git ls-files db.sqlite3)"

Artifacts:

  • Commit: 12fc12f955618b895f14e2109e24409206bc2fd6
  • PR: #135 (fix/staging-sqlite-artifact-131 -> main)
Implemented fix and opened PR for blocker. What changed: - Removed tracked `db.sqlite3` from repository so release/deploy source archives do not ship a stale SQLite DB artifact. - This removes the root-owned sqlite file path that caused `attempt to write a readonly database` during staging `migrate`. Checks run: - `bash -n infra/staging/deploy_staging.sh` - `test -z "$(git ls-files db.sqlite3)"` Artifacts: - Commit: `12fc12f955618b895f14e2109e24409206bc2fd6` - PR: #135 (`fix/staging-sqlite-artifact-131` -> `main`)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label devops need-to-have staging
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#131
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?