Marking all other packages/dev release as Invalid.
Per previous discussion with Jay, iirc, those are
leftovers from a previously considered solution(s)
which was not the final one (in initramfs-tools.)
And just Bionic had to be patched as later releases
were not affected.
Please feel free to fix
Thanks, Jay. Sorry for getting back late.
I just tested it on an 18.04.5 Ubuntu image, and just as you mentioned
it's working as expected. I think we can close this bug.
# ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
Si-Wei,
What environment and methodology are you testing with? I do not see the
same results you are reporting. I am using the instructions you
previously provided, and with an 18.04.5 Ubuntu image, I see the
expected network interface naming (ens3, ens3nsby), and do not see
/run/systemd/network
Jay,
The good news is that, with 0.130ubuntu3.11, initramfs-tools is now able
to render a correct netplan YAML file:
# cat /run/netplan/ens3.yaml
network:
version: 2
renderer: networkd
ethernets:
ens3:
set-name: ens3
dhcp4: true
dhcp-identifier: mac
critical: tru
Si-Wei,
In the test environment I'm using, the only change needed was to
initramfs-tools. I suspect the udevd change you're thinking of was an
alternate implementation that we did not proceed with due to the
regression it introduced (that network interface names would change).
--
You received t
I will get some time to test it this week. Are there other packages than
initramfs-tools that are deem required to make net_failover work on
Bionic? I recall there's some systemd-udevd level change needed not just
initramfs-tools that has to be fixed.
--
You received this bug notification becaus
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.11
---
initramfs-tools (0.130ubuntu3.11) bionic; urgency=medium
[ Guilherme G. Piccoli ]
* scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
The function _log_ms
This has been verified successfully on Bionic by @jvosburgh
on a (complex) internal test setup for 3-netdev naming work.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hello Si-Wei, or anyone else affected,
Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.11 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
To manage n
Uploaded initramfs-tools to Bionic.
Attaching the updated debdiff for reference.
(Rebased on top of the more recent -updates.)
** Tags added: sts-sponsor-mfo
** Patch added: "bionic_initramfs-tools_lp1879980_V3.debdiff"
https://bugs.launchpad.net/netplan/+bug/1820929/+attachment/5413642/+file
[sts-sponsor]
Sponsored in Bionic.
Thanks for your contribution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820929
Title:
netplan should consider adding more udev attribute for exact matching
Although the debdiff is hereby attached, 3 bugs have fixes carried on
such patch - the main work is done on LP ##1879980 (and the other LP
handled in this SRU is #1879987) .
** Tags added: sts
** Description changed:
- This bug is a follow-up to
+ [Impact]
- https://bugs.launchpad.net/ubuntu/
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubu
** Tags removed: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
To manage n
FWIW this is the 'udevadm info' output on the primary slave:
root@node-1970:~# udevadm info /sys/class/net/ens4
P: /devices/pci:00/:00:04.0/net/ens4
E: DEVPATH=/devices/pci:00/:00:04.0/net/ens4
E: ID_BUS=pci
E: ID_MODEL_FROM_DATABASE=82599 Ethernet Controller Virtual Function
E: ID
So what's your opinion for the disposition? I don't mind moving this bug
to initramfs-tools, but without having a way to identify the 3-netdev
master interface in netplan yaml config, thing still don't work there.
I'm not in a position to tell if it's possible for initramfs-tools to
remove the "mat
Yes, that does explain it.
/run/netplan/.yaml is written automatically by initramfs-
tools when booting with a remote root (ie. iscsi); so this does check
out: for example, 'critical' is required in that case, otherwise as soon
as someone runs 'netplan apply' the network will go down and you might
Before answering your quesitions, I would wonder what do you know
generates the /run/netplan/ens3.yaml file in the first place? This YAML
file is not provided by us obviously, the only netplan config we have on
the root disk is /etc/netplan/01-netcfg.yaml, derived from the debian
installer. The YAM
I also forgot to mention another entry I see in some of the configs:
set-name: ens3
If you do not need to explicitly rename the interfaces yourself to a
different name, I would avoid setting this at all. It *may* be being set
automatically by cloud-init (if that's in use, but the configs provided
All of these values should be coming directly from the netplan YAML. Are
all of these options required?
I see:
match:
macaddress: # Do you need to match the interface in this case? Is it
sufficient to match by name if only ens3 is being configured?
Also:
dhcp-identifier: mac # Th
Note only DHCP configuration exhibits this particular issue. The cause
is that when "dhcp4" is set to "yes" in the /etc/netplan/*.yaml config
file, netplan would generate a temporary per-interface yaml file under
/run/netplan, which matches interface using MAC address. While I don't
see this specif
There's barely anything can be used to distinguish but only the name (or
ifindex) itself.
root@node-1970:~# udevadm info /sys/class/net/ens3nsby
P: /devices/pci:00/:00:03.0/virtio0/net/ens3nsby
E: DEVPATH=/devices/pci:00/:00:03.0/virtio0/net/ens3nsby
E: ID_BUS=pci
E: ID_MODEL_FROM
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
To manage not
netplan is currently writing about as much as we can for the
networkd/udev configs; some values we don't know how to handle at all.
Looking at this, it feels to me like there will indeed be a need to find
a different data point to differentiate the interfaces, and MAC and
driver are not sufficient
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: sys
27 matches
Mail list logo