Tag: guest-builder
-
Side quest: the guest was reachable and its host was not
The first guest built on a chassis blade came up fine and answered on the network. The blade it ran on disappeared. No ping, no SSH, no management web interface, while the chassis still reported the blade as powered on.…
-
Side quest: systemctl start joined the run that had already read its inputs
A new alert rule was being proven the way every alert on this site is proven: induce the condition, then watch the rule react. The condition was induced correctly and the reading said nothing had happened. For a brand-new rule,…
-
Side quest: a mechanism that had never once worked
A Windows guest on the chassis gets a freshly minted, single-use Administrator password rather than one a caller supplied and the system never saw again. That password reaches the person who actually needs it as a one-time link, mailed to…
-
Side quest: a key that changes, and a fix that refuses to guess
The first guest build queued right after a blade’s redeploy failed with “REMOTE HOST IDENTIFICATION HAS CHANGED.” The blade had just been reimaged, which regenerates its SSH host key by design, and the builder’s own trusted-key list still held the…
-
Side quest: the home lab for actually testing things
Most of what gets built for this project runs somewhere that other things already depend on. The chassis behind this new series is not that. It exists specifically so that breaking something costs nothing beyond a power cycle, and every…
-
Side quest: the chassis that does not touch the fleet
A blade chassis showed up in this build’s corner of the world, and it is not part of the fleet this blog has been describing. It has its own tree, its own agent line, and its own set of decisions…