pdurlej/platform

Fork 0

fix(compose): repair minio-init one-shot before F3 migration #310

New issue

Closed

opened 2026-05-17 01:56:28 +02:00 by codex · 1 comment

codex commented

2026-05-17 01:56:28 +02:00

Collaborator

Context

During the 2026-05-17 F3 light/sidecar batch, operator requested minio-init together with coredns, honcho-api, honcho-deriver, and karakeep.

The other four were migrated/smoked successfully. minio-init was not safe to run as a normal F3 no-op smoke.

Evidence

modules/minio-init/module.yaml fails strict-v2 validation: missing intent.user_facing_outcome, intent.acceptance_criteria, and runtime image audit fields.
Live container: home-platform-minio-init-1 status=exited exit=1.
docker logs home-platform-minio-init-1 prints mc help output.
docker inspect home-platform-minio-init-1 shows entrypoint=["/bin/sh","-c"] and cmd=["mc","alias","set",...], which means the shell executes only mc instead of the full init script.
Canonical compose/core/compose.yaml currently renders the same broken shape in docker compose config minio-init.

Why this blocks F3 no-op smoke

platformctl-auto-apply.yml F3 is intentionally no-op-only: it refuses apply when the plan is not in-sync. Since the live init container is exited and the compose command shape is wrong, this needs a real fix/re-run path, not a no-op health smoke.

Suggested next path

Fix compose/core/compose.yaml so minio-init passes the whole command string as a single sh -c script.
Fill strict-v2 fields for modules/minio-init/module.yaml.
Decide the health contract for a one-shot init service: likely verify MinIO container health plus expected buckets, not home-platform-minio-init-1 running forever.
Run with explicit operator approval because this is a real one-shot apply, not a no-op F3 smoke.

References

PR #309 enabled the successful sidecar-bound Karakeep F3 path.
Issue #142 main RS2000 migration thread.

## Context During the 2026-05-17 F3 light/sidecar batch, operator requested `minio-init` together with `coredns`, `honcho-api`, `honcho-deriver`, and `karakeep`. The other four were migrated/smoked successfully. `minio-init` was not safe to run as a normal F3 no-op smoke. ## Evidence - `modules/minio-init/module.yaml` fails strict-v2 validation: missing `intent.user_facing_outcome`, `intent.acceptance_criteria`, and runtime image audit fields. - Live container: `home-platform-minio-init-1 status=exited exit=1`. - `docker logs home-platform-minio-init-1` prints `mc` help output. - `docker inspect home-platform-minio-init-1` shows `entrypoint=["/bin/sh","-c"]` and `cmd=["mc","alias","set",...]`, which means the shell executes only `mc` instead of the full init script. - Canonical `compose/core/compose.yaml` currently renders the same broken shape in `docker compose config minio-init`. ## Why this blocks F3 no-op smoke `platformctl-auto-apply.yml` F3 is intentionally no-op-only: it refuses apply when the plan is not in-sync. Since the live init container is exited and the compose command shape is wrong, this needs a real fix/re-run path, not a no-op health smoke. ## Suggested next path 1. Fix `compose/core/compose.yaml` so `minio-init` passes the whole command string as a single `sh -c` script. 2. Fill strict-v2 fields for `modules/minio-init/module.yaml`. 3. Decide the health contract for a one-shot init service: likely verify MinIO container health plus expected buckets, not `home-platform-minio-init-1` running forever. 4. Run with explicit operator approval because this is a real one-shot apply, not a no-op F3 smoke. ## References - PR #309 enabled the successful sidecar-bound Karakeep F3 path. - Issue #142 main RS2000 migration thread.

codex added the

labels

2026-05-17 01:56:28 +02:00

codex referenced this issue

2026-05-17 01:57:06 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142

codex referenced this issue

2026-05-17 03:05:20 +02:00

fix(f3): prepare minio stateful smoke #315

codex referenced this issue

2026-05-17 03:43:37 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142

codex referenced this issue

2026-05-17 08:03:07 +02:00

ops(forgejo): deploy-host runner intermittently fails to pick up waiting jobs #260

codex referenced this issue

2026-05-17 08:53:01 +02:00

docs(status): record RS2000 F3 closeout state #318

codex referenced this issue

2026-05-17 08:53:32 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142

codex referenced this issue

2026-05-17 08:59:40 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142

codex referenced this issue

2026-05-17 18:27:00 +02:00

docs(cutover): plan post-soak legacy cleanup #340

codex referenced this issue

2026-05-18 19:14:47 +02:00

fix(cutover): support minio-init one-shot apply #379

codex added this to the 01 - RS2000 closeout and legacy cleanup milestone

2026-05-19 08:36:19 +02:00

codex commented

2026-05-24 08:24:18 +02:00

Author

Collaborator

Codex Wave 1 M01 closeout — resolved by minio-init one-shot fix

Role: executor
Action: closing as resolved

Evidence checked read-only on RS2000:

release root: /opt/pdurlej-platform/current -> releases/c6928decfb42e12756ca4cd638fa66c704ba9498
home-platform-minio-init-1: exited exit=0
home-platform-minio-1: running health=healthy
minio-init logs show successful bucket bootstrap for artifacts, archives, and backups-staging
modules/minio-init/module.yaml now has strict-v2 intent/runtime fields and expected_state: exited-success
modules/minio-init/runbook.md documents the one-shot health contract and operator-gated rerun procedure
compose/core/compose.yaml now passes the full script through sh -c (entrypoint: ["/bin/sh"], command: [-c, | ...])

No production mutation was performed by this comment; checks were read-only.

## Codex Wave 1 M01 closeout — resolved by minio-init one-shot fix **Role:** executor **Action:** closing as resolved Evidence checked read-only on RS2000: - release root: `/opt/pdurlej-platform/current -> releases/c6928decfb42e12756ca4cd638fa66c704ba9498` - `home-platform-minio-init-1`: `exited exit=0` - `home-platform-minio-1`: `running health=healthy` - minio-init logs show successful bucket bootstrap for `artifacts`, `archives`, and `backups-staging` - `modules/minio-init/module.yaml` now has strict-v2 intent/runtime fields and `expected_state: exited-success` - `modules/minio-init/runbook.md` documents the one-shot health contract and operator-gated rerun procedure - `compose/core/compose.yaml` now passes the full script through `sh -c` (`entrypoint: ["/bin/sh"]`, `command: [-c, | ...]`) No production mutation was performed by this comment; checks were read-only.

codex referenced this issue

2026-05-24 08:24:18 +02:00

meta(roadmap): execute post-soak legacy cleanup flight #387

codex closed this issue

2026-05-24 08:24:18 +02:00