Jonathan Lebon

Do you have `passwd` and `group` from https://github.com/coreos/fedora-coreos-config/tree/testing-devel/manifests in your source config?

That error is likely just a symptom of an earlier failure. Look for errors from e.g. Ignition or `ignition-ostree-mount-firstboot-sysroot.service`.

Prow flaked on network, but CI doesn't test this anyway. /override ci/prow/images /override ci/prow/rhcos

Some commits of interest: - https://github.com/coreos/coreos-assembler/commit/1817ead0a13527fe78f674755fc11de085ef466b - https://github.com/coreos/coreos-assembler/commit/a12a54949eb716da5e58d79d9c3a767a0760c71e

Converting to draft. @dustymabe said he's willing to try this out locally with this patch (thanks!). So let's try that first. If for whatever reason the only way to reliably...

Ahhh, can you try again with `-v`? (Edit: or change the `Infof` to `fmt.Printf` I guess)

OK, I kinda spent a bit more time than I should've on this. But I think this can be a really useful tool in the kit for helping to debug...

Yeah, the SSH bit is tricky, even though these are just throwaway test VMs. The other approach I did was to just persist it to disk. But I'm trying to...

> Hmm, how about: we hardcode a public SSH key in kola, put the private key in BitWarden, and have kola add the key to all test VMs it spawns...

How about we have `KOLA_LEAK_ON_FAIL` actually be the pubkey to use?