Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-54380

SriovNetworkNodeState stuck in InProgress

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • Yes
    • None
    • None
    • CNF Network Sprint 269
    • 1
    • In Progress
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      Description of problem: After the VF mtu is reset when it is moved from pod to host, the sriovnodestate is stuck at InProgress status instead of Succeeded.

      Version-Release number of selected component (if applicable): 4.19.0

      How reproducible: 100% 

      Steps to Reproduce:
      1. Create 2 VFs with mtu1500 and attach to 2 pods
      2. Modify mtu of net1 interface in pod1 and then delete the pod1
      3. VF should be moved to host and the mtu should be reset to 1500

      4. SriovNodeState is still in InProgress

      Actual results:  SriovNodeState stuck in InProgress

      Expected results: SriovNodeState moves to Succeeded after it is in InProgress for brief moment

       

      Error Message:

      2025-03-06T18:11:18.75130024Z ERROR updateSyncState retry/util.go:51 failed to update node state status {"SyncStatus": "InProgress", "LastSyncError": "", "error": "Operation cannot be fulfilled on sriovnetworknodestates.sriovnetwork.openshift.io \"worker-0\": the object has been modified; please apply your changes to the latest version and try again"}

              sscheink@redhat.com Sebastian Scheinkman
              rh-ee-ajaggapa Anvesh Jaggapatruni
              None
              None
              Anvesh Jaggapatruni Anvesh Jaggapatruni
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: