Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-12240

BZ#2162522 NetworkManager connections are created automatically for every VF

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • os-net-config
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Set
    • None
    • Low

      Description of problem:
      Somehow NetworkManager connections are created automatically for every VF, so there are a lot of DHCPREQUEST packets due to that (DHCP is enabled on those connection profiles).

      Version-Release number of selected component (if applicable):
      os-net-config-11.5.1-2.20211207004924.el8ost.noarch

      How reproducible:
      Deploy compute node with the following snippet for SR-IOV PFs interfaces in the nic-config template:
      ~~~

      • type: sriov_pf
        name: ens2f0
        mtu: 9000
        numvfs: 32
        use_dhcp: false
        defroute: false
        nm_controlled: true
        hotplug: true
        promisc: true
      • type: sriov_pf
        name: ens2f1
        mtu: 9000
        numvfs: 32
        use_dhcp: false
        defroute: false
        nm_controlled: true
        hotplug: true
        promisc: false
      • type: sriov_pf
        name: ens3f0
        mtu: 9000
        numvfs: 32
        use_dhcp: false
        defroute: false
        nm_controlled: true
        hotplug: true
        promisc: true
      • type: sriov_pf
        name: ens3f1
        mtu: 9000
        numvfs: 32
        use_dhcp: false
        defroute: false
        nm_controlled: true
        hotplug: true
        promisc: false
        ~~~

      Steps to Reproduce:
      1. Deploy compute node
      2. Check NM connections with `nmcli conn`

      Actual results:
      ~~~
      [jmarti@supportshell-1 sosreport-overcloud-computehci-6-2023-01-18-emnywvj]$ grep -E 'connection.interface-name.ens.f.v.+' sos_commands/networkmanager/nmcli_con_show_id_
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_10:connection.interface-name: ens2f0v8
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_100:connection.interface-name: ens3f0v30
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_101:connection.interface-name: ens3f0v23
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_102:connection.interface-name: ens3f0v31
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_103:connection.interface-name: ens3f0v15
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_104:connection.interface-name: ens3f0v0
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_105:connection.interface-name: ens2f1v11
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_106:connection.interface-name: ens3f1v10
      sos_commands/networkmanager/nmcli_con_show_id_Wired_connection_108:connection.interface-name: ens3f1v24
      ...
      ~~~

      Expected results:
      No NM connection profiles related to VFs.

      Additional info:
      There are no ifcfg files related to the VFs on `/etc/sysconfig/network-scripts/`.
      The PF related files are like this:
      ~~~

      1. This file is autogenerated by os-net-config
        DEVICE=ens2f0
        ONBOOT=yes
        HOTPLUG=no
        NM_CONTROLLED=yes
        PEERDNS=no
        BOOTPROTO=none
        MTU=9000
        DEFROUTE=no
        ~~~

      sosreports and templates available here: https://one.redhat.com/attachment-viewer/viewer?caseNumber=03415766

              rhn-engineering-dsneddon Dan Sneddon
              jira-bugzilla-migration RH Bugzilla Integration
              RH Bugzilla Integration RH Bugzilla Integration
              rhos-dfg-nfv
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: