The last-green LaSuite upgrade bases referenced the removed docker.io/minio/minio image, stopping both lifecycle suites before deployment.
Add exact-version previous/ overlays for docs 0.4.0+v5.4.1 and drive 0.12.0+v0.21.0. Pin the available MinIO build by digest, bypass its distribution wrapper, and retain the published /data layout, secret files and bucket initialization. The repair is stripped before upgrading to the recipe PR head.
Live verification exposed two runner defects fixed here: previous/ repair files tripped Abra's clean-tree gate, and a failed second convergence sample after restore escaped the retry budget. Explicitly check out the base version before deploying its overlay through the existing chaos mechanism; ordinary pinned deployments retain their gate. Keep both convergence observations inside the existing timeout, with persistent failures still failing.
docs PR #11, ae725c7e00ef: Drone build 92 SUCCESS, install/upgrade/backup/restore/custom all PASS, level 5/5, clean teardown and secret checks PASS.
drive PR #8, 93c9d1a9b047: Drone build 93 SUCCESS, the same five stages and checks PASS, level 5/5.
Both recipe PR commit checks updated to success. Recipe PRs remain open.
16 focused unit tests PASS, including red/green regression controls for base checkout/deploy ordering and transient versus persistent convergence failures. Full lint and latest push self-test #90 PASS.
Adjacent runner sample has one pre-existing test_no_head_version_skips_tag_lookup_uses_main failure, independently reproduced on unchanged main.
The live /etc/cc-ci checkout was fast-forwarded to the merge; its unrelated local modifications were preserved. No host rebuild required. No assertions or lifecycle stages weakened or skipped.
The last-green LaSuite upgrade bases referenced the removed docker.io/minio/minio image, stopping both lifecycle suites before deployment.
Add exact-version previous/ overlays for docs 0.4.0+v5.4.1 and drive 0.12.0+v0.21.0. Pin the available MinIO build by digest, bypass its distribution wrapper, and retain the published /data layout, secret files and bucket initialization. The repair is stripped before upgrading to the recipe PR head.
Live verification exposed two runner defects fixed here: previous/ repair files tripped Abra's clean-tree gate, and a failed second convergence sample after restore escaped the retry budget. Explicitly check out the base version before deploying its overlay through the existing chaos mechanism; ordinary pinned deployments retain their gate. Keep both convergence observations inside the existing timeout, with persistent failures still failing.
Verified after merge at 8356c4aee7b1:
- docs PR #11, ae725c7e00ef: [Drone build 92](https://drone.ci.autonomic.zone/recipe-maintainers/cc-ci/92) SUCCESS, install/upgrade/backup/restore/custom all PASS, level 5/5, clean teardown and secret checks PASS.
- drive PR #8, 93c9d1a9b047: [Drone build 93](https://drone.ci.autonomic.zone/recipe-maintainers/cc-ci/93) SUCCESS, the same five stages and checks PASS, level 5/5.
- Both recipe PR commit checks updated to success. Recipe PRs remain open.
- 16 focused unit tests PASS, including red/green regression controls for base checkout/deploy ordering and transient versus persistent convergence failures. Full lint and latest push self-test #90 PASS.
- Adjacent runner sample has one pre-existing test_no_head_version_skips_tag_lookup_uses_main failure, independently reproduced on unchanged main.
The live /etc/cc-ci checkout was fast-forwarded to the merge; its unrelated local modifications were preserved. No host rebuild required. No assertions or lifecycle stages weakened or skipped.
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.
The last-green LaSuite upgrade bases referenced the removed docker.io/minio/minio image, stopping both lifecycle suites before deployment.
Add exact-version previous/ overlays for docs 0.4.0+v5.4.1 and drive 0.12.0+v0.21.0. Pin the available MinIO build by digest, bypass its distribution wrapper, and retain the published /data layout, secret files and bucket initialization. The repair is stripped before upgrading to the recipe PR head.
Live verification exposed two runner defects fixed here: previous/ repair files tripped Abra's clean-tree gate, and a failed second convergence sample after restore escaped the retry budget. Explicitly check out the base version before deploying its overlay through the existing chaos mechanism; ordinary pinned deployments retain their gate. Keep both convergence observations inside the existing timeout, with persistent failures still failing.
Verified after merge at
8356c4aee7:The live /etc/cc-ci checkout was fast-forwarded to the merge; its unrelated local modifications were preserved. No host rebuild required. No assertions or lifecycle stages weakened or skipped.