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

Node status doesn't report resource created by new SriovNetworkNodePolicy

    XMLWordPrintable

Details

    • CNF Network Sprint 229, CNF Network Sprint 230
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      11/30: removing from the Telco-Grade OCP 4.12 gating list since it's not reproducible in 4.12, will track the backport
      11/28: Green. Not reproduceable on 4.12; suggesting the be removed from the gating list.
      11/21: Y e l l o w. Triage in progress.
      11/14: added to the Telco-Grade OCP 4.12 gating list
      Show
      11/30: removing from the Telco-Grade OCP 4.12 gating list since it's not reproducible in 4.12, will track the backport 11/28: Green. Not reproduceable on 4.12; suggesting the be removed from the gating list. 11/21: Y e l l o w. Triage in progress. 11/14: added to the Telco-Grade OCP 4.12 gating list

    Description

      Description of problem:

      Node status doesn't report resources created by new SriovNetworkNodePolicy.

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

      4.10.41
      sriov-network-operator.4.10.0-202211041323

      How reproducible:

      100%

      Steps to Reproduce:

      1. Deploy SNO DU with Telco profile
      
      2. Create a new SriovNetworkNodePolicy, in addition to existing ones
      
      apiVersion: sriovnetwork.openshift.io/v1
      kind: SriovNetworkNodePolicy
      metadata:
        name: snnp1
        namespace: openshift-sriov-network-operator
      spec:
        deviceType: vfio-pci
        isRdma: false
        nicSelector:
          pfNames:
          - ens2f3#32-33
        nodeSelector:
          node-role.kubernetes.io/master: ""
        numVfs: 48
        priority: 99
        resourceName: snnp1
      
       3.Wait for the node to report the `snnp1` resource
      
      
      

      Actual results:

      snnp1 is not reported by the node:
      
      [kni@registry.kni-qe-0 ~]$ oc get nodes sno.kni-qe-1.lab.eng.rdu2.redhat.com -o json | jq .status.allocatable
      {
        "cpu": "44",
        "ephemeral-storage": "499572036Ki",
        "hugepages-1Gi": "32Gi",
        "hugepages-2Mi": "0",
        "intel.com/intel_fec_acc100": "16",
        "management.workload.openshift.io/cores": "48k",
        "memory": "63419304Ki",
        "openshift.io/du_fh": "16",
        "openshift.io/du_mh": "16",
        "openshift.io/pci_sriov_net_f1": "2",
        "pods": "250"
      }
      [kni@registry.kni-qe-0 ~]$ oc get nodes sno.kni-qe-1.lab.eng.rdu2.redhat.com -o json | jq .status.capacity
      {
        "cpu": "48",
        "ephemeral-storage": "499572036Ki",
        "hugepages-1Gi": "32Gi",
        "hugepages-2Mi": "0",
        "intel.com/intel_fec_acc100": "16",
        "management.workload.openshift.io/cores": "48k",
        "memory": "98100136Ki",
        "openshift.io/du_fh": "16",
        "openshift.io/du_mh": "16",
        "openshift.io/pci_sriov_net_f1": "2",
        "pods": "250"
      }
      

      Expected results:

      "openshift.io/du_mh": "2" in the node status

      Additional info:

      Attaching must-gather and sriovnetworknodestate.

      Attachments

        Issue Links

          Activity

            People

              sscheink@redhat.com Sebastian Scheinkman
              mcornea@redhat.com Marius Cornea
              Marius Cornea Marius Cornea
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: