The appliance gate stays red until the redis layer is published #10

New issue

Open

opened 2026-09-28 02:23:30 -03:00 by marcos-mendez · 0 comments

marcos-mendez commented

2026-09-28 02:23:30 -03:00

(Migrated from github.com)

Opened 2026-09-28. This issue exists to own a red check and to give it an end,
not to report a surprise.

Once Keel-Linux/.github#12 merges, appliance / boot-published-layer on this
repository fails on every pull request, with:

::error::https://mirror.keellinux.org/layers/redis.manifest answers 404:
the redis layer has never been published, so this job cannot boot it and
will not report that it did

Measured, not predicted: run 36373971968 of this repository, a temporary pull
request pointed at that branch, concluded failure in 12 seconds.

That is the correct state and it is deliberate. Before the change this job
concluded success in 11 seconds having pulled, verified and booted nothing
(run 36369705307 on #5), which is what made #5 look ready to merge. The
allow_unpublished exemption exists for a repository whose first layer does
not exist yet, and this one is not bootstrapping: it has a recipe, a boot test
and a layer waiting to be built, so the exemption is deliberately not used
here.

Nothing is blocked meanwhile. Branch protection on master requires
tests / coverage and package / changelog only, not this check.

What closes this: build redis on the build host (bt-layer redis) and
publish it (docs/releases-host.md, publishing a layer). The next run then
pulls, verifies, assembles and boots it, and the check goes green by booting
something.

Why it has an issue at all: a standing red that nobody owns teaches everyone
to ignore red. docs/traps.md of the handbook records that shape already, and
keel-nodejs-nginx#3 is the other one open today. Honest red is only honest
while it is short-lived and has a name against it.

Opened 2026-09-28. This issue exists to own a red check and to give it an end, not to report a surprise. Once Keel-Linux/.github#12 merges, `appliance / boot-published-layer` on this repository fails on every pull request, with: ::error::https://mirror.keellinux.org/layers/redis.manifest answers 404: the redis layer has never been published, so this job cannot boot it and will not report that it did Measured, not predicted: run 36373971968 of this repository, a temporary pull request pointed at that branch, concluded failure in 12 seconds. That is the correct state and it is deliberate. Before the change this job concluded **success** in 11 seconds having pulled, verified and booted nothing (run 36369705307 on #5), which is what made #5 look ready to merge. The `allow_unpublished` exemption exists for a repository whose first layer does not exist yet, and this one is not bootstrapping: it has a recipe, a boot test and a layer waiting to be built, so the exemption is deliberately not used here. Nothing is blocked meanwhile. Branch protection on `master` requires `tests / coverage` and `package / changelog` only, not this check. What closes this: build `redis` on the build host (`bt-layer redis`) and publish it (docs/releases-host.md, publishing a layer). The next run then pulls, verifies, assembles and boots it, and the check goes green by booting something. Why it has an issue at all: a standing red that nobody owns teaches everyone to ignore red. `docs/traps.md` of the handbook records that shape already, and keel-nodejs-nginx#3 is the other one open today. Honest red is only honest while it is short-lived and has a name against it.