Skip to content

fix: Database mode and network confirm screens say only what is true - #18

Merged
marcos-mendez merged 2 commits into
masterfrom
fix/console-screens-tell-the-truth
Oct 2, 2026
Merged

marcos-mendez merged 2 commits into
masterfrom
fix/console-screens-tell-the-truth

Conversation

@marcos-mendez

@marcos-mendez marcos-mendez commented Oct 2, 2026 •

Copy link
Copy Markdown
Collaborator

Two confconsole screens from the maintainer's screenshots of the Core image (2026-10-02). confconsole 2.2.3+keel11 (master took keel9 and keel10; master is merged in).

  • 045, Database mode > Cloud > Primary on a machine with no database server. Root cause: dbscreen.engine_of appended everything keel inspect printed on stderr to the no-server text. inspect had written its spec, so that stderr was about other fields: here "required fields not inferred: instance.fqdn". The screen now shows only the no-server text. (keel 0.15.1, fix: inspect, confirm and monit on a Keel Core (keel#60, keel#61) keel#64, also stops requiring the fqdn.)
  • 040, Overlay network confirm. Root cause: the verdict for exit 21 said "the change reverts when its window ends unless a new session confirms it", whatever keel's reason. keel also refuses when nothing is waiting, for example after another session confirmed it. The verdict is now "not confirmed: the reason is above", and keel's own line says which. With keel 0.15.1, a change already confirmed returns exit 0 and says so.

Tests written first: 643 pass, 5 skip; the measured modules stay at 100 percent lines and branches.

Real test: LXC container from the step 7b Core image with this package, keel 0.15.1, inithooks keel15 and keel-core 0.1.1; Primary showed only the no-server text, and the console confirm after an lxc-attach confirm showed "already confirmed ... it stays", exit 0. Container destroyed.

  • CI green
  • Review

navigator added 2 commits October 2, 2026 03:48
Database mode on a machine with no database server no longer appends
keel inspect's stderr, which is about other fields (a missing fqdn in
the maintainer's screenshot 045). The verdict of a refused keel network
confirm (exit 21) no longer claims the change reverts when its window
ends: keel refuses for several reasons, nothing waiting among them, as
when another session confirmed it already (screenshot 040); it now
points at keel's own line.
master took 2.2.3+keel10 (the Keel Linux names) after keel9 (the
console art); this branch's entry becomes 2.2.3+keel11 above them.
@marcos-mendez
marcos-mendez merged commit 0f38fc8 into master Oct 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant