K-S3 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
27.1's first start upgrades the store layout one way. Orchestrators need a mode that does only that and exits: 0 when done (or nothing to do), non-zero on failure. It refuses if another node holds the lease.
Done when
inbuxa --config … --upgrade-store runs the upgrade and exits with a clear log line
Idempotent: a second run exits 0 and changes nothing
Refuses while another node is running
Integration test
Depends on: S5
**K-S3** · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
27.1's first start upgrades the store layout one way. Orchestrators need a mode that does only that and exits: 0 when done (or nothing to do), non-zero on failure. It refuses if another node holds the lease.
**Done when**
- `inbuxa --config … --upgrade-store` runs the upgrade and exits with a clear log line
- Idempotent: a second run exits 0 and changes nothing
- Refuses while another node is running
- Integration test
**Depends on:** S5
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 05:14:39 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-S3 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
27.1's first start upgrades the store layout one way. Orchestrators need a mode that does only that and exits: 0 when done (or nothing to do), non-zero on failure. It refuses if another node holds the lease.
Done when
inbuxa --config … --upgrade-storeruns the upgrade and exits with a clear log lineDepends on: S5
Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Reopened: closed in the tracker cleanup but not done. Now in PR #448, docs in inbuxa/inbuxa.org#168.
Fixed in #448, merged to main; ships in the next 27.1 release candidate.