5 Commits

Include renames

Author	SHA1	Message	Date
autonomic-bot	bb2e3c6b2c	feat(prevb): dynamic upgrade base (last-green→main→skip) + per-recipe previous/ overlay; migrate discourse off static base + leaky overlay ... - resolve_upgrade_base: BasePlan(kind=version|ref|skip); last-green (warm canonical) primary, main-tip fallback, declared skip else. UPGRADE_BASE_VERSION retained as optional override. - deploy_app: base_ref path (chaos-deploy a main-tip/last-green commit) + apply_previous wiring. - lifecycle: previous/ surface (has_previous, previous_target_version, previous_status decision, provide/remove overlay, compose_file add/remove, recipe_branch_commit, stack_service_names). - generic.perform_upgrade: strip previous/ overlay + COMPOSE_FILE entry before head redeploy. - discourse: compose.ccci.yml now environmental-only (order: stop-first); removed bitnamilegacy pins + sidekiq + UPGRADE_BASE_VERSION; test_upgrade.py asserts head image == official 3.5.3 + no sidekiq. - unit tests: resolve_upgrade_base matrix + previous/ apply/skip/stale + COMPOSE_FILE layering.	2026-06-17 00:15:06 +00:00
autonomic-bot	0cc31a507e	fix(dstamp): discourse upgrade stop-first overlay (stop 2x-memory start-first OOM→spurious swarm rollback) + harness assert_upgrade_converged (detect rollback/pause → honest upgrade failure, HC1 unweakened). Root cause: failure_action:rollback reverted chaos-version label, masked by start-first+wait_healthy	2026-06-11 17:07:38 +00:00
autonomic-botandClaude Opus 4.8	8dfd8ed3b3	fix(2): discourse — revert non-working depends_on override (additive map-merge can't remove bad key); keep image warm-cache + 3600s timeout ... The depends_on:[app] override in 04cc44c does NOT make compose valid: docker normalizes short-form depends_on to a map and merges additively, so {discourse}+{app}={discourse,app} keeps the invalid 'discourse' key (config --images still rc=15). Reverted to keep the overlay minimal (re-pin + grace only). Prepull-skip is harmless because bitnamilegacy/discourse:3.3.1 is warm in the node image cache → inline pull is a no-op. Timeout headroom (3600s) retained in recipe_meta. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-31 01:25:47 +00:00
autonomic-botandClaude Opus 4.8	04cc44c15e	fix(2): discourse base-deploy timeout — prepull-enable (sidekiq depends_on app, valid compose) + 3600s timeout ... full4 base deploy timed out at 2400s on the 7-GiB single node. Root causes: (1) sidekiq.depends_on referenced undefined service 'discourse' (main svc is 'app') → abra config --images rc=15 → prepull SKIPPED → 2.4GB image pulled inline during deploy, eating convergence budget. Overlay now overrides sidekiq.depends_on:[app] (swarm ignores depends_on → no-op at runtime, masks nothing) so prepull resolves+pre-pulls images on both base+head deploys. (2) bumped DEPLOY_TIMEOUT/TIMEOUT 2400→3600 for headroom on the RAM/CPU-constrained Rails cold boot. Also pre-cached bitnamilegacy/discourse:3.3.1 by tag on cc-ci (was dangling <none>). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-31 01:23:38 +00:00
autonomic-botandClaude Opus 4.8	845b86c868	feat(2): discourse Q4.6 — upgrade-to-latest 0.7.0 base-repin+grace overlay (compose.ccci.yml) ... Per Adversary course-correction (bdef282) + plan-ccci-compose-overlay-policy.md §1: upgrade-to-latest is MANDATORY. The 0.7.0+3.3.1 from-version pins the Docker-Hub-removed bitnami/discourse:3.3.1 (404) and ships a too-tight 5m start_period for the 15-25min Rails cold boot. Minimal base overlay compose.ccci.yml re-pins app+sidekiq to bitnamilegacy/discourse:3.3.1 (namespace-only, identical image — same re-pin the PR head makes) + widens start_period to 20m (grace-only). install_steps.sh provides it; CHAOS_BASE_DEPLOY skips the clean-tree gate; UPGRADE_BASE_VERSION=0.7.0+3.3.1 sets the true predecessor. Neither change weakens a test. Run shape returns to STAGES=install,upgrade,backup, restore,custom. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-30 19:29:41 +00:00