My previous understanding was flawed. I anticipated that renaming the
00-installer-config.yaml to 10-livefs.yaml (because 00-installer-
config.yaml is special to Subiquity) would work but it doesn't.
The main problem is that Subiquity and netplan (or the underlying
network daemon, really) have different understandings of priority when
multiple network configs match for the same interface. (obviously
netplan should be considered right and ideally Subiquity should defer to
netplan).
For instance, in the following situation:
/etc/netplan/00-installer-config.yaml
network: 2
version:
ethernets:
zz-all-en:
match:
name: "en*"
dhcp4: true
/etc/netplan/50-cloud-init.yaml
network
version: 2
ethernets:
enc600:
addresses: [10.245.236.23/24]
1. netplan (systemd-networkd) decides to honor the static addressing from
50-cloud-init.yaml.
Indeed the generated conf files for systemd-networkd are:
* /run/systemd/network/10-netplan-enc600.network
* /run/systemd/network/10-netplan-zz-all-en.network
Quote from systemd.network(5):
> The network file contains a [Match] section, which determines if a given
> network file may
> be applied to a given interface; and a [Network] section specifying how the
> interface
> should be configured. The first (in alphanumeric order) of the network files
> that matches
> a given interface is applied, all later files are ignored, even if they match
> as well.
so 10-netplan-enc600.network (generated from /etc/netplan/50-cloud-
init.yaml) is honored.
2. Subiquity decides to honor DHCP addressing because it takes the first
matching config from /etc/netplan/*.yaml (and it reads 00-installer-
config.yaml before 50-cloud-init.yaml).
In an ideal world, Subiquity should use the same logic as netplan but
netplan defers to the underlying network daemon so that will be a
challenging task. Maybe going forward Subiquity should read the
currently active network config (e.g., netplan status?) rather than
parsing /etc/netplan?
In any case, we have a few options today:
* Rename 00-installer-config.yaml to 60-livefs.yaml. This will not impact
netplan but will impact make Subiquity give more priority to 50-cloud-init.yaml
* Drop 00-installer-config.yaml completely
* Change Subiquity so that it guesses better which config will be used after
netplan apply.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583
Title:
Current questing daily installation hangs on NW config screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
