This bug was fixed in the package systemd - 245.4-4ubuntu3.19
---
systemd (245.4-4ubuntu3.19) focal; urgency=medium
[ dann frazier ]
* Add support for the v247 network naming scheme, but keep v245 as default
(LP: #1945225)
Author: dann frazier
Files:
-
debian/patc
Verification:
Before:
ubuntu@akis:~$ ls /sys/class/net
enp134s0f0 enp230s0 enp93s0 ens103 eth0 eth7
enp134s0f1 enp6s0ens102 ens107 eth2 lo
After upgrade to systemd 245.4-4ubuntu3.19 (w/ net.naming-scheme=v247):
ubuntu@akis:~$ ls /sys/class/net
enp134s0f0 enp184s0 enp225s0 enp53s
Hello dann, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.19 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429491
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/194
I was not able to make the .link approach work, even in an installed
environment. I fought with it for a while during spurts of machine
access. Without that, I was not able to move on to the next step of
trying to insert it into a commissioning script.
--
You received this bug notification becaus
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1945225
Title:
udev produces unpredictable net names when PCI device is a bridge
Status in s
Thanks for the investigation, I'm 100% +1 on comment #5.
The MR introduces some (low) risk of breaking existing use cases (#5.1),
while not fixing the issue for anyone directly. Instead, it provides an
(easier/additional?) workaround to the issue, which still needs to be
applied to any individual
So with regards to MAAS, if you wish to apply the link file, I'd second
adding a commissioning script that writes the file and executes early
enough in the commissioning process (scripts execute in the order of
their names, i.e 40-my-script will execute before 50-my-other-script).
You can then also
Thanks for checking in @ddstreet. I haven't found an alternate way yet -
but I also haven't exhausted alternatives. I've got an open request w/
the MAAS team for which I'm awaiting a response.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
did you find any alternate way to handle this? If not we should probably
review/merge the 247 naming approach, if @slyon approves
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bu
> I like the idea of the kernel command line argument because it is
easy to apply and consistent across install types.
I agree the kernel boot param is absolutely easier, especially in the
context of maas.
TL;DR from me is: I think it's at least worth looking at using a link
file, or some other
OK, I'll reach out to the MAAS team to see if they have a good
recommendation. To be clear of my goals here - I'm confident that I
could come up with a workaround that would work for my environment. My
goal here is to come up with an easy-to-apply workaround for other users
of such systems. I like
> how would one insert such a file during (and early enough) in the
commissioning process?
well, i'll leave that one up to the maas team to answer properly, but i think
there are ways to use custom commissioning scripts:
https://maas.io/docs/commissioning-scripts-reference
or even custom commiss
On Wed, Oct 13, 2021 at 05:10:05PM -, Dan Streetman wrote:
> > udev can produce unpredictable network interface names by default when
> multiple devices map to the same slot due to an intermediate bridge.
>
> so, if I understand it right, the MR won't actually fix this for anyone
> without add
> udev can produce unpredictable network interface names by default when
multiple devices map to the same slot due to an intermediate bridge.
so, if I understand it right, the MR won't actually fix this for anyone
without additional per-system work, right? specifically, any system with
this proble
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/409304
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/194
** Changed in: systemd (Ubuntu Impish)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => dann f
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Description changed:
[Impact]
ude
18 matches
Mail list logo
