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

Applying VF Configuration again and again fails

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-9.4.z
    • nmstate
    • No
    • Moderate
    • rhel-sst-network-management
    • ssg_networking
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat OpenStack Services on OpenShift (formerly Red Hat OpenStack Platform)
    • None
    • Hide

      Given a system with SR-IOV enabled and a PF properly configured using Nmstate, 

      When a VF configuration is applied using Nmstate for the first time or re-applied afterwards, 

      Then, the VF configurations are successfully created or updated without errors.

      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 SR-IOV enabled and a PF properly configured using Nmstate,  When a VF configuration is applied using Nmstate for the first time or re-applied afterwards,  Then, the VF configurations are successfully created or updated without errors. 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

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

      Apply the VF configuration (attached as tigon31_nms_2.yaml) repeatedly

      What is the impact of this issue to you?

      Cannot re-apply the VF configuration again.

      Please provide the package NVR for which the bug is seen:

      [root@compute-1 ~]# nmstatectl --version
      nmstatectl 2.2.33
      [root@compute-1 ~]# nmcli -v
      nmcli tool, version 1.46.0-19.el9_4

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1. Apply the PF config - tigon31_nms.yaml
      2. Apply the VF config - tigon31_nms_2.yaml -> Fails
      [2024-11-12T09:04:22Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for [373/29263]
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:22Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:22Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:22Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:22Z INFO  nmstate::nm::query_apply::profile] Will retry activation 8 seconds                                                             
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Activating connection 1c5dd9e7-ab74-4c39-9977-0a66f1f99f7a: ens1f1v0/802-3-ethernet         
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Activating connection 59ce8d14-0e47-4ce4-9b84-d1a014aa77b8: ens1f1v1/802-3-ethernet         
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Activating connection 01ca7419-72e4-437c-87f5-de32cb2bcec7: ens1f2v0/802-3-ethernet         
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Activating connection 7a35e4ef-6d37-400f-bea5-a39c3907e1e0: ens1f2v1/802-3-ethernet         
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:30Z INFO  nmstate::nm::query_apply::profile] Will retry activation 16 seconds                                                            
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Activating connection 1c5dd9e7-ab74-4c39-9977-0a66f1f99f7a: ens1f1v0/802-3-ethernet         
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Activating connection 59ce8d14-0e47-4ce4-9b84-d1a014aa77b8: ens1f1v1/802-3-ethernet         
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Activating connection 01ca7419-72e4-437c-87f5-de32cb2bcec7: ens1f2v0/802-3-ethernet         
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Activating connection 7a35e4ef-6d37-400f-bea5-a39c3907e1e0: ens1f2v1/802-3-ethernet         
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connec
tion (device eno12399 not available because profile is not compatible with device (mismatching interface name)).                                           
[2024-11-12T09:04:46Z INFO  nmstate::nm::query_apply::profile] Will retry activation 32 seconds
      1. Apply the VF config again - Fails with an error
      [2024-11-12T09:12:16Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Verification failure: ens1f1.interface.ethernet.sr-[101/29263]
fs desire '5', current '0'                                                                                                                                 
[2024-11-12T09:12:18Z INFO  nmstate::query_apply::net_state] Retrying on: SrIovVfNotFound: Failed to find VF 0 interface name of PF ens1f1                 
[2024-11-12T09:12:19Z INFO  nmstate::query_apply::net_state] Retrying on: SrIovVfNotFound: Failed to find VF 0 interface name of PF ens1f1

       

      Expected results

      The Vfs shall be created and configured

      Actual results

      The Vfs are created but cannot be configured

        1. tigon31_nms_2.yaml
          7 kB
        2. tigon31_nms.yaml
          1 kB

              rh-ee-sfaye Stanislas Faye
              ksundara@redhat.com Karthik Sundaravel
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: