Comment # 2 on bug 1172413 from Ludwig Nussel

What do you mean with two configs? The way we ship MicroOS appliances relies on
a successful ignition run. If the first boot fails to fetch a config, be it
forgotten usb stick or network glitch, the system still boots, exposes it's ssh
port but is otherwise useless. No way to log in or manage the system. Power
cycling won't fix the situation.

One has to redeploy the image or or mount the image on another system and touch
the ignition trigger file again. Pretty annoying.

So what is your suggestion to make this smarter?