Don't let switches out of reloading until they finish reconfiguring too.
I'm not sure exactly why this was originally like this (let the node out of reloading before doing the console-based reconfiguration --- cleaning out the old config and writing a default one, via the console), but it now fails because the node gets released from reloading (and thus its reservation is cleared) before the reconfiguration step can grab the console line via tiptunnel --- and a subsequent tiptunnel connect fails, presumably because the reload_daemon no longer has permission to grab the line. Anyway, we'll try this... I can't see any obvious negative side effects.
Showing with 3 additions and 1 deletion