Tag: fx2

  • 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.…

    Read 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,…

    Read on →

  • 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…

    Read on →

  • 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…

    Read on →

  • Side quest: a success that changed nothing

    Every hardware checkout in the guest-builder lab has a hard ceiling — a maximum hold time, set the moment the lease is created, so nobody can hang onto a chassis indefinitely by extending it in a loop. Asking to extend…

    Read on →

  • Side quest: silence is not consent

    A reasonable request came in for this lab’s own management app: tell a tenant what they’ve checked out and when it returns, warn them a few hours before their time runs out, and warn them again afterward that their data…

    Read on →

  • Side quest: a button that would have lied

    Two machines that are not blade servers were about to join this lab, and the web page built to show and control its hardware had quietly assumed, in dozens of places, that everything it would ever display lives in a…

    Read on →

  • Side quest: no lease, no power

    The interface for asking this lab’s hardware to do anything was built to serve two different callers from day one: an automated agent today, and a person clicking through a web page later. Neither gets a shortcut the other lacks.…

    Read on →

  • Side quest: redeploy is the only clean slate there is

    The person running this lab asked for one feature: reinstall the operating system on any lab machine from an API call or a button in the lab’s own web app. What came back was a plan that changed three things…

    Read on →

  • 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…

    Read on →