From d63bf320f90702f5b0429ca24ccd231161a5163f Mon Sep 17 00:00:00 2001 From: Ubuntu Date: Sat, 2 May 2026 10:37:41 +0800 Subject: [PATCH 1/2] docs: add usercron path migration note to upgrade SOP --- docs/ai-install-upgrade.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/ai-install-upgrade.md b/docs/ai-install-upgrade.md index 43ba2168..587f0a8a 100644 --- a/docs/ai-install-upgrade.md +++ b/docs/ai-install-upgrade.md @@ -104,6 +104,13 @@ rollback openab per the upgrade SOP — the upgrade to v0.7.7 failed > **Gateway config migration (one-time, if applicable):** If you previously enabled a custom gateway by manually patching the ConfigMap (e.g. adding `[gateway]` to `config.toml` by hand), that block is not captured by `helm get values`. Before upgrading, copy the gateway settings into your `values.yaml` under `agents..gateway` and set `enabled: true` so they are preserved on every subsequent `helm upgrade`. See chart `values.yaml` for the field reference (`enabled`, `url`, `platform`, `token`, `botUsername`). After migrating, do not manually edit the ConfigMap again — manage gateway config through `values.yaml` only. +> **Usercron path migration (v0.8.2+):** The usercron `cronjob.toml` path resolution changed from `$HOME/` to `$HOME/.openab/`. If you have an existing `cronjob.toml` in the agent's home directory, move it before upgrading: +> ``` +> mkdir -p $HOME/.openab +> mv $HOME/cronjob.toml $HOME/.openab/cronjob.toml +> ``` +> The scheduler will not pick up the file from the old location. Hot-reload (polling every 60s) will detect the file once it is in the correct path. + --- ## 3. Upgrade @@ -142,6 +149,10 @@ rollback openab per the upgrade SOP — the upgrade to v0.7.7 failed │ errors in logs; verify Cloudflare tunnel URL │ │ is still reachable and update values.yaml if │ │ the URL has rotated │ + │ ✓ (if usercron enabled) cronjob.toml loaded │ + │ — check for "loaded usercron jobs" in logs; │ + │ if count=0, verify file is at │ + │ $HOME/.openab/cronjob.toml (not $HOME/) │ │ │ │ ALL PASS ──► proceed to 6. CLEANUP │ │ ANY FAIL ──► proceed to 5. ROLLBACK │ From 22d8dbabd2dca606c450bd50db66ec24059522e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E8=B6=85=E6=B8=A1=E6=B3=95=E5=B8=AB?= Date: Sun, 3 May 2026 11:16:18 +0000 Subject: [PATCH 2/2] fix(docs): align smoke test log guidance with runtime behavior The smoke test previously told operators to check for 'loaded usercron jobs' with count=0, but src/cron.rs only emits that message when count > 0. When the file is missing or empty, the actual log message is 'no cronjobs yet, but usercron_path is set'. Updated the guidance to reference the correct failure-mode signal. --- docs/ai-install-upgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ai-install-upgrade.md b/docs/ai-install-upgrade.md index 587f0a8a..3609fa2d 100644 --- a/docs/ai-install-upgrade.md +++ b/docs/ai-install-upgrade.md @@ -151,8 +151,8 @@ rollback openab per the upgrade SOP — the upgrade to v0.7.7 failed │ the URL has rotated │ │ ✓ (if usercron enabled) cronjob.toml loaded │ │ — check for "loaded usercron jobs" in logs; │ - │ if count=0, verify file is at │ - │ $HOME/.openab/cronjob.toml (not $HOME/) │ + │ if you see "no cronjobs yet" instead, verify │ + │ file is at $HOME/.openab/cronjob.toml │ │ │ │ ALL PASS ──► proceed to 6. CLEANUP │ │ ANY FAIL ──► proceed to 5. ROLLBACK │