CentOS 8 - depmod warning, systemd-modules-load.service changed

I just ran a dnf update on CentOS 8 to do the usual package updates and, among other updates, there was:

Installing: kernel               x86_64 4.18.0-240.10.1.el8_3           baseos       4.3 M kernel-core          x86_64 4.18.0-240.10.1.el8_3           baseos        30 M kernel-devel         x86_64 4.18.0-240.10.1.el8_3           baseos        17 M kernel-modules       x86_64 4.18.0-240.10.1.el8_3           baseos        26 M

and

Removing: kernel               x86_64 4.18.0-193.28.1.el8_2           @BaseOS        0 kernel-core          x86_64 4.18.0-193.28.1.el8_2           @BaseOS       60 M kernel-devel         x86_64 4.18.0-193.28.1.el8_2           @BaseOS       47 M kernel-modules       x86_64 4.18.0-193.28.1.el8_2           @BaseOS       20 M

during the cleanup process, it said:

warning: file /lib/modules/4.18.0-193.28.1.el8_2.x86_64/updates: remove failed: No such file or directory

and after cleanup

dkms: running auto installation service for kernel 4.18.0-240.10.1.el8_3.x86_64Kernel preparation unnecessary for this kernel.  Skipping...Building module:cleaning build area....make -j8 KERNELRELEASE=4.18.0-240.10.1.el8_3.x86_64 -C /lib/modules/4.18.0-240.10.1.el8_3.x86_64/build M=/var/lib/dkms/snapapi26/0.7.135/build....cleaning build area....DKMS: build completed.snapapi26.ko.xz:Running module version sanity check. - Original module   - No original module exists within this kernel - Installation   - Installing to /lib/modules/4.18.0-240.10.1.el8_3.x86_64/extra/snumbd26.ko.xz:Running module version sanity check. - Original module   - No original module exists within this kernel - Installation   - Installing to /lib/modules/4.18.0-240.10.1.el8_3.x86_64/extra/Adding any weak-modulesdepmod....Warning: The unit file, source configuration file or drop-ins of systemd-modules-load.service changed on disk. Run 'systemctl daemon-reload' to reload units.DKMS: install completed. Done.

Then I took a closer look at the issue:

$ systemctl --failed  UNIT                           LOAD   ACTIVE SUB    DESCRIPTION● kdump.service                  loaded failed failed Crash recovery kernel arm>● NetworkManager-wait-online.service loaded failed failed Network Manager Wait >

$ systemctl status systemd-modules-load● systemd-modules-load.service - Load Kernel Modules   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static>   Active: inactive (dead)Condition: start condition failed at Sun 2021-01-31 13:55:58 PST; 7min ago     Docs: man:systemd-modules-load.service(8)           man:modules-load.d(5)

NetworkManager was fixed with a systemctl restart, and I tried disabling kdump just in case. After that systemctl --failed returns 0 loaded units listed.

Then

$ systemctl daemon-reload

$ systemctl restart systemd-modules-load

$ systemctl status systemd-modules-load● systemd-modules-load.service - Load Kernel Modules   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static>   Active: inactive (dead)Condition: start condition failed at Sun 2021-01-31 14:05:43 PST; 5s ago├─ ConditionDirectoryNotEmpty=|/lib/modules-load.d was not met├─ ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d was not met├─ ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d was not>├─ ConditionDirectoryNotEmpty=|/etc/modules-load.d was not met├─ ConditionDirectoryNotEmpty=|/run/modules-load.d was not met├─ ConditionKernelCommandLine=|modules-load was not met└─ ConditionKernelCommandLine=|rd.modules-load was not met     Docs: man:systemd-modules-load.service(8)           man:modules-load.d(5)

/usr/modules contains the modules but /usr/modules-load.d is empty.

$ ls -Al /lib/modulestotal 12drwxr-xr-x. 7 root root 4096 Jan 31 13:55 4.18.0-193.6.3.el8_2.x86_64drwxr-xr-x. 7 root root 4096 Jan 31 13:56 4.18.0-240.10.1.el8_3.x86_64drwxr-xr-x. 6 root root 4096 Jan 31 13:55 4.18.0-240.1.1.el8_3.x86_64

Same pattern for all other directories it's complaining about.

For your information

$ uname -aLinux server01 4.18.0-193.6.3.el8_2.x86_64 #1 SMP Wed Jun 10 11:09:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I tried to include as much info as possible. What went wrong, and how I can fix it? I have not tried rebooting or doing anything until I had some insight first. Thank you.