recipe-maintainers/plausible
0
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

revert: restore sleep 10 (needed for pgautoupgrade window) #5

Open
autonomic-bot wants to merge 5 commits from upgrade-4.0.0+v3.2.1 into main
pull from: upgrade-4.0.0+v3.2.1
merge into: :main
Conversation 18 Commits 5 Files Changed 4
+40 -9
autonomic-bot commented 2026-06-29 18:59:42 +00:00
Owner
Copy Link
Copy Source

Recipe upgrade.

Commits on top of upstream main:

  • 3a8e0dd revert: restore sleep 10 (needed for pgautoupgrade window)
  • b5cf2a9 chore: drop sleep 10 from app command (align with upstream v3)
  • 161fe5e fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for root element
  • ad6b93a fix: update .env.sample for CE v3.x SMTP requirements and add config versions
  • 78124a5 chore: upgrade to ghcr.io/plausible/community-edition:v3.2.1

Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.

cc @trav @notplants

Recipe upgrade. Commits on top of upstream main: - 3a8e0dd revert: restore sleep 10 (needed for pgautoupgrade window) - b5cf2a9 chore: drop sleep 10 from app command (align with upstream v3) - 161fe5e fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for <clickhouse> root element - ad6b93a fix: update .env.sample for CE v3.x SMTP requirements and add config versions - 78124a5 chore: upgrade to ghcr.io/plausible/community-edition:v3.2.1 Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review. cc @trav @notplants
autonomic-bot added 2 commits 2026-06-29 18:59:43 +00:00
chore: upgrade to ghcr.io/plausible/community-edition:v3.2.1 78124a5076 
- Switch app image from plausible/analytics:v2.0.0 to
  ghcr.io/plausible/community-edition:v3.2.1 (image registry changed at v3.x)
- Bump ClickHouse from 23.4.2.11-alpine to 24.12-alpine (required for CE v3.x)
- Add CLICKHOUSE_SKIP_USER_SETUP=1 env var to ClickHouse service (required for v3.0.0+)
- Add ClickHouse healthcheck
- Update clickhouse-user-config.xml: replace deprecated <yandex> root with
  <clickhouse> root; adopt CE low-resource profile settings for < 16 GB RAM hosts
fix: update .env.sample for CE v3.x SMTP requirements and add config versions
cc-ci/testme cc-ci: failure
Details
ad6b93a1f4
autonomic-bot requested review from trav 2026-06-29 18:59:43 +00:00
autonomic-bot requested review from notplants 2026-06-29 18:59:43 +00:00
autonomic-bot commented 2026-06-29 18:59:52 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-06-29 19:00:17 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ ad6b93a1 ❌ failure

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `ad6b93a1` ❌ **failure** [![cc-ci result card](https://ci.commoninternet.net/runs/968/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/968) [![level](https://ci.commoninternet.net/runs/968/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/968) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/968) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot changed title from upgrade: plausible v2.0.0 → v3.2.1, clickhouse 23.4 → 24.12 to fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for <clickhouse> root element 2026-07-13 23:58:21 +00:00
autonomic-bot added 1 commit 2026-07-13 23:58:22 +00:00
fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for <clickhouse> root element
cc-ci/testme cc-ci: failure
Details
161fe5e4d6
autonomic-bot commented 2026-07-13 23:58:26 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-07-13 23:58:56 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ 161fe5e4 ❌ failure

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `161fe5e4` ❌ **failure** [![cc-ci result card](https://ci.commoninternet.net/runs/1127/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1127) [![level](https://ci.commoninternet.net/runs/1127/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1127) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1127) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot changed title from fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for <clickhouse> root element to chore: drop sleep 10 from app command (align with upstream v3) 2026-07-14 00:24:12 +00:00
autonomic-bot added 1 commit 2026-07-14 00:24:12 +00:00
chore: drop sleep 10 from app command (align with upstream v3)
cc-ci/testme cc-ci: failure
Details
b5cf2a9dd4
autonomic-bot commented 2026-07-14 00:24:15 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-07-14 00:24:31 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ b5cf2a9d ❌ failure

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `b5cf2a9d` ❌ **failure** [![cc-ci result card](https://ci.commoninternet.net/runs/1128/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1128) [![level](https://ci.commoninternet.net/runs/1128/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1128) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1128) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot changed title from chore: drop sleep 10 from app command (align with upstream v3) to revert: restore sleep 10 (needed for pgautoupgrade window) 2026-07-14 00:37:08 +00:00
autonomic-bot added 1 commit 2026-07-14 00:37:10 +00:00
revert: restore sleep 10 (needed for pgautoupgrade window)
cc-ci/testme cc-ci: failure
Details
867ebfafed
autonomic-bot commented 2026-08-07 05:15:05 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-08-07 05:15:17 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ 867ebfaf ❌ failure

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `867ebfaf` ❌ **failure** [![cc-ci result card](https://ci.commoninternet.net/runs/1224/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1224) [![level](https://ci.commoninternet.net/runs/1224/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1224) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1224) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot commented 2026-08-11 05:24:10 +00:00
Author
Owner
Copy Link
Copy Source

The upgrade itself is fine — the RED is a stale cc-ci test. Diagnosed on cc-ci against this PR head (867ebfaf).

install, upgrade, backup and restore all pass. Only the three custom tests fail, for two reasons that are both in the tests:

  1. v3 only ingests events for a site that belongs to a TEAM. The custom tier registered a sites row and nothing else, which was enough for v2. Under community-edition v3 a teamless site is dropped — POST /api/event still returns 202 and the postgres row still exists, so it looks like a silent ingestion stall. ClickHouse names the reason itself in ingest_counters: dropped_not_found with 0 rows; link a team and it flips to buffered and the rows land. Verified both ways on cc-ci.
  2. The post-restore health wait was 60s. The custom tier runs after backup/restore, which restarts the app, and v3 boots through sleep 10 → createdb → migrate → cache warmers first.

Test fix: cc-ci#17. With that branch, the full cold suite against this PR head is GREEN, level 5 of 5 — all three previously-failing tests pass. Neither change weakens an assertion: the event tests still require the row to reach ClickHouse and match what was sent, and the health test still requires a hard 200.

Dependent pair: !testme here runs the deployed cc-ci tests, so this PR stays RED until cc-ci#17 merges. Merge that first, then re-run !testme here.

One unrelated thing to fix before release: compose.yml still carries coop-cloud.${STACK_NAME}.version=3.1.0+v2.0.0, which does not match this upgrade.

**The upgrade itself is fine — the RED is a stale cc-ci test.** Diagnosed on cc-ci against this PR head (`867ebfaf`). `install`, `upgrade`, `backup` and `restore` all pass. Only the three custom tests fail, for two reasons that are both in the tests: 1. **v3 only ingests events for a site that belongs to a TEAM.** The custom tier registered a `sites` row and nothing else, which was enough for v2. Under `community-edition` v3 a teamless site is dropped — `POST /api/event` still returns 202 and the postgres row still exists, so it looks like a silent ingestion stall. ClickHouse names the reason itself in `ingest_counters`: `dropped_not_found` with 0 rows; link a team and it flips to `buffered` and the rows land. Verified both ways on cc-ci. 2. **The post-restore health wait was 60s.** The custom tier runs after backup/restore, which restarts the app, and v3 boots through `sleep 10` → `createdb` → `migrate` → cache warmers first. Test fix: **[cc-ci#17](https://git.autonomic.zone/recipe-maintainers/cc-ci/pulls/17)**. With that branch, the full cold suite against this PR head is **GREEN, level 5 of 5** — all three previously-failing tests pass. Neither change weakens an assertion: the event tests still require the row to reach ClickHouse and match what was sent, and the health test still requires a hard 200. **Dependent pair:** `!testme` here runs the *deployed* cc-ci tests, so this PR stays RED until cc-ci#17 merges. Merge that first, then re-run `!testme` here. One unrelated thing to fix before release: `compose.yml` still carries `coop-cloud.${STACK_NAME}.version=3.1.0+v2.0.0`, which does not match this upgrade.
autonomic-bot commented 2026-08-11 14:52:32 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-08-11 14:52:58 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ 867ebfaf ❌ failure → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1239

(summary card unavailable — see the run for details.) full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `867ebfaf` ❌ **failure** → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1239 _(summary card unavailable — see the run for details.)_ [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1239) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot commented 2026-08-11 14:57:05 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-08-11 14:57:20 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ 867ebfaf ❌ failure → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1240

(summary card unavailable — see the run for details.) full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `867ebfaf` ❌ **failure** → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1240 _(summary card unavailable — see the run for details.)_ [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1240) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot commented 2026-08-11 15:12:06 +00:00
Author
Owner
Copy Link
Copy Source

Test fix is merged — but do not read the red !testme badge as a plausible failure

cc-ci#17 and
cc-ci#18 are merged, so main now
carries the fixed fixture.

This PR's suite passes. Verified by running the harness the same way !testme does — full cold
suite, this PR head (867ebfaf), from a fresh clone of cc-ci main:

install : pass   upgrade : pass   backup : pass   restore : pass   custom : pass
level = 5 of 5   VERDICT: GREEN

All three previously-failing tests pass. That result has now been reproduced three times.

!testme is separately broken right now, and it is not this recipe. Builds 1239 and 1240 both
report failure but produce no run artifacts at all — no results.json, no summary card — so the
harness never completed. The last build to produce results was 1235; nothing since 1236 has, which
predates today's test change. Two other CI-side problems are visible on the host and are worth
looking at together:

  • the cc-ci push lint gate is red on main independently of this work — 91 files fail
    ruff format and tests/unit/test_f211_sso_skip.py fails ruff check C420. A 91-file reformat is
    an operator call, so I have not touched it.
  • the warm-gitea canonical is down (0/1), crash-looping on
    failed to save "/etc/gitea/app.ini": read-only file system.

I could not read drone's build log to pin the exact cause — it needs a drone token, and the bridge
container that holds one is distroless with no shell. That is the next thing to check.

Still outstanding on this PR before release: compose.yml carries
coop-cloud.${STACK_NAME}.version=3.1.0+v2.0.0, which does not match this upgrade.

### Test fix is merged — but do not read the red `!testme` badge as a plausible failure [cc-ci#17](https://git.autonomic.zone/recipe-maintainers/cc-ci/pulls/17) and [cc-ci#18](https://git.autonomic.zone/recipe-maintainers/cc-ci/pulls/18) are merged, so `main` now carries the fixed fixture. **This PR's suite passes.** Verified by running the harness the same way `!testme` does — full cold suite, this PR head (`867ebfaf`), from a **fresh clone of cc-ci `main`**: ``` install : pass upgrade : pass backup : pass restore : pass custom : pass level = 5 of 5 VERDICT: GREEN ``` All three previously-failing tests pass. That result has now been reproduced three times. **`!testme` is separately broken right now**, and it is not this recipe. Builds 1239 and 1240 both report failure but produce **no run artifacts at all** — no `results.json`, no summary card — so the harness never completed. The last build to produce results was **1235**; nothing since 1236 has, which predates today's test change. Two other CI-side problems are visible on the host and are worth looking at together: - the cc-ci **push lint gate is red on `main`** independently of this work — 91 files fail `ruff format` and `tests/unit/test_f211_sso_skip.py` fails `ruff check` C420. A 91-file reformat is an operator call, so I have not touched it. - the **`warm-gitea` canonical is down (0/1)**, crash-looping on `failed to save "/etc/gitea/app.ini": read-only file system`. I could not read drone's build log to pin the exact cause — it needs a drone token, and the bridge container that holds one is distroless with no shell. That is the next thing to check. **Still outstanding on this PR before release:** `compose.yml` carries `coop-cloud.${STACK_NAME}.version=3.1.0+v2.0.0`, which does not match this upgrade.
autonomic-bot commented 2026-08-11 15:30:39 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-08-11 15:30:40 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ 867ebfaf ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `867ebfaf` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/1243/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1243) [![level](https://ci.commoninternet.net/runs/1243/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1243) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1243) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot commented 2026-08-11 17:22:46 +00:00
Author
Owner
Copy Link
Copy Source

!testme

!testme
autonomic-bot commented 2026-08-11 17:22:46 +00:00
Author
Owner
Copy Link
Copy Source

🌻 cc-ci — plausible @ 867ebfaf ❌ failure → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1248

(summary card unavailable — see the run for details.) full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `867ebfaf` ❌ **failure** → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1248 _(summary card unavailable — see the run for details.)_ [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1248) · [dashboard](https://ci.commoninternet.net/)
Some required checks failed
cc-ci/testme cc-ci: failure
Details
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin upgrade-4.0.0+v3.2.1:upgrade-4.0.0+v3.2.1
git checkout upgrade-4.0.0+v3.2.1
Sign in to join this conversation.
Reviewers
No Reviewers
trav
notplants
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
autonomic autonomic-bot kawaiipunk (KawaiiPunk) notplants trav (Trav Fryer)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/plausible#5