Comment 6 for bug 2017278

Possible changes:

## Making the desktop installer mark the network model configured again after a user connects to a network.
As long as Subiquity reevaluates the status of the network (but see below), it should update has_network accordingly.

Downsides:

 * When Subiquity evaluates the status of the network, it ignores temporary routes that NM spawned to test the connection (they have metric >= 20000). Consequently, evaluating the status of the network immediately after a user connects to a network using NM will likely cause Subiquity to treat the network as down.
 * Marking the network model configured does not make Subiquity automatically reevaluate the status. Only probert events do. There is no guarantee how long it would take for a new event to occur - although it is expected to be quite fast.

## Making the desktop installer mark the network model configured again after a user connects to a network + tell subiquity if we're online or not.

Downsides:

* It delegates the knowledge of the network status to the desktop installer.

## Marking the network model configured later in the process (e.g., after selecting the storage)

This is probably the simplest approach at the moment.

Downsides:

* Not really a long term solution. Currently, the desktop installer does not explicitly request mirror testing - which is something we would want it to do going forward. Because it is not explicitly requested, mirror testing will happen automatically at a later stage, during the installation. Explicitly requesting mirror testing earlier would help figure out if the connection is setup properly - and will provide the ability to failover to an offline install if needed.
Mirror testing does not run until the network model is configured.