On Sun, 2021-06-13 at 19:19 +0800, Ed Greshko wrote:
On 13/06/2021 19:07, Patrick O'Callaghan wrote:
> On Sun, 2021-06-13 at 09:02 +0800, Ed Greshko wrote:
> > On 13/06/2021 08:41, Samuel Sieb wrote:
> > > So that gave me the clue that led to the real problem. The
> > > service
> > > is included in the initrd and masking it on the system doesn't
> > > change that. Even re-creating the initrd with dracut after
> > > masking
> > > didn't change anything.
> > >
> > > And also the nm-initrd.service file is in dracut, so you would
> > > have
> > > to modify it there (not the system one) to change this.
> > FWIW, I had a VM which needed a kernel update.
> >
> > Prior to the update it had references to systemd-udev-
> > settle.service
> > in the logs.
> >
> > I edited /usr/lib/dracut/modules.d/35network-manager/nm-
> > initrd.service to have
> >
> > DefaultDependencies=no
> > #Wants=systemd-udev-settle.service
> > #After=systemd-udev-settle.service
> > After=dracut-cmdline.service
> >
> > And I installed the latest kernel.
> >
> > Now....
> >
> > [egreshko@f34x ~]$ systemctl status systemd-udev-settle.service ○
> > systemd-udev-settle.service
> > Loaded: masked (Reason: Unit systemd-udev-settle.service
> > is
> > masked.)
> > Active: inactive (dead)
> >
> > And nothing in the logs about systemd-udev-settle
> Interesting. Wouldn't that count as a bug in nm-initrd.service?
>
Well, to me, it would mean a bugzilla should be written against the
dracut-network package requesting the
file be modified to eliminate the log entries.
You're probably right. Either way, it should probably be reported.
poc