Comment 10 for bug 1854965

I tried this again carefully today and think the originally reported problem is solved.

Subiquity now correctly reports that the network is not up by "Continue without network" (since subiquity seems to try a automatic network configuration by default that is not possible in my case/environment), allows to configure the network (what I did statically), I can then proceed with "Save" and "Done" and the network is properly configured, up and running. So regarding this flow everything is fine and this ticket can be closed.

However, all the network configuration data was already passed over via the parm-file.
So it would be good and convenient if it's just picked up by subiquity and automatically activated, so that this second static config becomes obsolete ...