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
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
Bugs, which is subscribed to
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945225
Title:
udev
> 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
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
> 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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945225
Title:
udev
** 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
** 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]
11 matches
Mail list logo
