GRI-1885: fix smoke-test db profile and config.toml permission #124
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!124
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/GRI-1885-env-compose-profile"
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?
Two fixes to
scripts/mvp-smoke-test.sh, found while running the real client-against-server smoke test for GRI-1885:.envnever setCOMPOSE_PROFILES=bundled-db, so the bundled database never started.config.tomlis written into a path under the agent home directory, where a default ACL made it unreadable to the container's uid (Permission denied); the script nowchmods it 0644 and strips the ACL before the bind mount.Both were diagnosed and verified end-to-end on the build host: with both fixes applied, the stack (server, db, real client) now comes up, connects, and gets through device approval.
Test plan
./scripts/local-gates.shpasses