tree 4f143be7218443701acf6fb1830762a4a749c34d
parent c5d28e49c53c7dd0b1f88160514342a1e1b98958
author Lorenz Brun <lorenz@monogon.tech> 1726609486 +0200
committer Lorenz Brun <lorenz@monogon.tech> 1726684288 +0000

m/node/core: fix nodeparams dependent on network

The GCP nodeparams gathering strategy depends on network availability.
With the introduction of static network configuration that got added to
NodeParameters which meant that they needed to be there before the
network could be initialized. This dependency loop stalls bootup on GCP
forever.

Fix it by splitting up NodeParameter gathering into a local and a
non-local phase. In setups where metadata is gathered via network
automated network configuration is generally always available to break
this dependency loop. Thus we can start networking after the local phase
has finished and run the non-local (i.e. networked) phase later.

Change-Id: I661b9b474f67f2289f427327efa4c3eaa19393e7
Fixes: https://github.com/monogon-dev/monogon/issues/353
Reviewed-on: https://review.monogon.dev/c/monogon/+/3439
Reviewed-by: Leopold Schabel <leo@monogon.tech>
Tested-by: Jenkins CI