What were you trying to do that didn't work?

Customers making use of their own naming scheme through having /etc/systemd/network/*.link files see issues because their naming is not applied during boot.
This is because both dracut network modules reference an invalid path:

        [[ $hostonly ]] && inst_multiple -H -o "${systemdsystemconfdir}/network/*.link"

Here above systemdsystemconfdir is used, which expands to /etc/systemd/system instead of some missing new systemdnetworkconfdir property which would expand to /etc/systemd/network.

This got fixed Upstream by following commits:

commit 744c6de5cde38d012f93bc53f9076bf9c37b8b72
Author: Antonio Alvarez Feijoo <antonio.feijoo@suse.com>
Date:   Mon Jul 11 13:08:57 2022 +0200

    fix(network-manager): correct wrong local network configuration path

---

commit 2eb733cc11c09358b79e2c73218953f5bb64da93
Author: Antonio Alvarez Feijoo <antonio.feijoo@suse.com>
Date:   Mon Jul 11 13:08:40 2022 +0200

    fix(network-legacy): correct wrong local network configuration path

Please make sure /usr/lib/dracut/dracut.conf.d/01-dist.conf is fixed, it's not defining systemdnetworkconfdir at all, there was a refactoring Upstream which brought that in, but it's not directly cherry-pickable.

Please provide the package NVR for which bug is seen:

dracut-057-44.git20230822.el9

How reproducible:

Always

Steps to reproduce

1. Create a .link file in /etc/systemd/network
2. Rebuild the initramfs

Expected results

.link file embedded in the initramfs

Actual results

Not embedded