Description of problem:
In Azure, if enable SR-IOV, there must be a rule to make NetworkManager ignore the SRIOV interface:
cat /etc/udev/rules.d/68-azure-sriov-nm-unmanaged.rules:

1. Accelerated Networking on Azure exposes a new SRIOV interface to the VM.
2. This interface is transparently bonded to the synthetic interface,
3. so NetworkManager should just ignore any SRIOV interfaces.
   SUBSYSTEM=="net", DRIVERS=="hv_pci", ACTION=="add", ENV {NM_UNMANAGED}

   ="1"

This rule works in RHEL-8. However, it doesn't work in RHEL-9. The NetworkManager-wait-online.service still fail:

[root@wala90719sriov08050847-vm1 ~]# systemd-analyze blame
1min 27ms NetworkManager-wait-online.service

[root@wala90719sriov08050847-vm1 ~]# systemctl status NetworkManager-wait-online
× NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-08-05 06:31:13 EDT; 13s ago
Docs: man:nm-online(1)
Process: 767 ExecStart=/usr/bin/nm-online -s -q (code=exited, status=1/FAILURE)
Main PID: 767 (code=exited, status=1/FAILURE)
CPU: 48ms

Aug 05 06:30:13 wala90719sriov08050847-vm1 systemd[1]: Starting Network Manager Wait Online...
Aug 05 06:31:13 wala90719sriov08050847-vm1 systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Aug 05 06:31:13 wala90719sriov08050847-vm1 systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'.
Aug 05 06:31:13 wala90719sriov08050847-vm1 systemd[1]: Failed to start Network Manager Wait Online.

Version-Release number of selected components (if applicable):

RHEL Version:
RHEL-9.0(5.14.0-0.rc3.29.el9.x86_64)
NetworkManager-1.32.2-1.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot up a RHEL-9 VM on Azure with a SR-IOV card
2. Add a rule: /etc/udev/rules.d/68-azure-sriov-nm-unmanaged.rules (content is in the description)
3. systemctl status NetworkManager-wait-online

Actual results:
Service failed and costs ~1min30s on every boot.

Expected results:
Service runs successfully.

Additional info:
This rule is manually added.