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

A customer installs a RHEL9 system through booting the DVD and using a kickstart specifying a bond configuration, e.g.:

network  --bootproto=dhcp --device=bond0 --bondslaves=enp1s0,enp2s0 --bondopts=mode=active-backup --noipv6 --activate --hostname=test --onboot=on

This leads to getting "rogue" network interfaces configured as well, instead of expected "bond0" and its slaves:

# nmcli con show
NAME           UUID                                  TYPE      DEVICE 
bond0          a95cb2de-d677-4506-af66-f258eba3d17e  bond      bond0  
bond0_slave_1  86338e9a-ff13-4dd1-bc93-be551d17488f  ethernet  enp1s0 
bond0_slave_2  17e9e0dc-5294-4613-a59e-e54bdf144c0e  ethernet  enp2s0 
lo             9f1f0363-2258-4538-8379-5105598b2ad1  loopback  lo     
enp1s0         f765bb53-3cbe-3b8d-a51b-c11395b0bce2  ethernet  --     
enp2s0         06fd36d2-5b51-3538-82e2-31929269bf4c  ethernet  --     

Here above "enp1s0" and enp2s0" are not expected to exist at all.
After the installation complete, this results in having too many files in /etc/NetworkManager/system-connections/ directory.

This is a regression compared to RHEL8.9, where we get this below:

# nmcli con show
NAME                   UUID                                  TYPE      DEVICE 
Bond connection bond0  6dbe6164-7698-49c6-8820-67f61fc089c6  bond      bond0  
bond0 slave 1          15e0634e-1fd2-4e12-bef2-1cd90deb4bff  ethernet  enp1s0 
bond0 slave 2          3eb628c1-576b-46a2-9efb-1a83966088cb  ethernet  enp2s0 

I'm filing this against NetworkManager because it appears it's NetworkManager that pre-configures enp1s0 and enp2s0 as Wired connection 1 respectively Wired connection 2 before kickstart executes (at least before %pre script).
These interfaces get IP addresses as well (so are auto-configured).
Later the interfaces are renamed into enp1s0 and enp2s0 by some unknown mechanism.

Please provide the package NVR for which bug is seen:

NetworkManager-1.46.0-4.el9_4

How reproducible:

Always

Steps to reproduce

1. Create a OEMDRV disk to contain attached kickstart (which configures a bond)

   # mkdir OEMDRV
   # cp /tmp/ks.cfg OEMDRV/
   # mkisofs -V OEMDRV -o OEMDRV.iso OEMDRV

2. Boot the system with DVD attached and OEMDRV attached as well as 2nd DVD

Expected results

Only bond being configured and files in /mnt/sysroot/etc/NetworkManager/system-connections/ reflecting this.

Actual results

1. No pre-configuration of native network interfaces before kickstart executes
2. Native network interfaces not having files in /mnt/sysroot/etc/NetworkManager/system-connections/