Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-69125

'connection-activate' should not reset SRIOV sriov_numvfs if unchanged

XMLWordPrintable

    • No
    • Moderate
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Refine next
    • Hide

      Given a system with SRIOV configured and VFs in use,

      When the connection-activate command is used without changing SRIOV settings,

      Then NetworkManager should not reset the sriov_numvfs value. This way unnecessary purging and re-adding of VFs is avoided. 

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are written and pass 
      • The code is part of a downstream build attached to an errata
      Show
      Given a system with SRIOV configured and VFs in use, When the connection-activate command is used without changing SRIOV settings, Then NetworkManager should not reset the sriov_numvfs value. This way unnecessary purging and re-adding of VFs is avoided.  Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass  The code is part of a downstream build attached to an errata
    • None
    • None
    • None

      With SRIOV settings not changed, when invoking the DBUS call `'connection-activate`, NM will set the SRIOV sriov_numvfs to 0 and set it back to original value. This will break OpenShift and OpenStack usage as the VF NICs will be purged and re-added.

              rh-ee-sfaye Stanislas Faye
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: