Spuriuous boot time configuration failure

[Frode Nordahl]

$ systemctl status sriov-netplan-shim
● sriov-netplan-shim.service - Configure SR-IOV VF functions on boot
     Loaded: loaded (/lib/systemd/system/sriov-netplan-shim.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2021-05-04 13:48:01 UTC; 1h 7min ago
   Main PID: 969 (code=exited, status=1/FAILURE)

May 04 13:48:01 node-laveran sriov-netplan-shim[969]: INFO:root:Configuring SR-IOV device enp3s0f0np0 with 32 VF's
May 04 13:48:01 node-laveran sriov-netplan-shim[969]: sriov-netplan-shim: [Errno 2] No such file or directory: '/sys/class/net/enp3s0f0np0/device/sriov_numvfs'
May 04 13:48:01 node-laveran systemd[1]: sriov-netplan-shim.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:48:01 node-laveran systemd[1]: sriov-netplan-shim.service: Failed with result 'exit-code'.
May 04 13:48:01 node-laveran systemd[1]: Failed to start Configure SR-IOV VF functions on boot.

$ sudo cat /etc/sriov-netplan-shim/interfaces.yaml
interfaces:
  enp3s0f0:
    match:
      pciaddress: '0000:03:00.0'
    num_vfs: 32
  enp3s0f1:
    match:
      pciaddress: '0000:03:00.1'
    num_vfs: 32

I wonder if we can access the same sysfs node using the PCI address or if we need to retry or if we need to re-order startup sequence (again).

[Frode Nordahl (fnordahl)]

Fixed by https://github.com/openstack-charmers/sriov-netplan-shim/pull/5