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

ZTP reference needs to allow SriovNetworkNodePolicy to be customizeable

XMLWordPrintable

    • None
    • Telco kube-compare Sprint 259
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      Running cluster-compare with the current RAN reference shows a difference in the SriovNetworkNodePolicy when that should be allowed.
          

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

      ZTP upstream git (master branch as of 2024-08-26)
          

      How reproducible:

      100%
          

      Steps to Reproduce:

          1. Deploy an SNO with ZTP and the DU profile, with a valid node-specific SriovNetworkNodePolicy
          2. Run the cluster-compare tool against the ZTP RAN reference
      
          

      Actual results:

      Differences found in CR: sriovnetwork.openshift.io/v1_SriovNetworkNodePolicy_openshift-sriov-network-operator_sriov-nnp-du-fh, Compared To Reference CR: required/sriov-operator/SriovNetworkNodePolicy.yaml
      diff -u -N /tmp/MERGED-1505123141/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-fh /tmp/LIVE-676221210/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-fh
      --- /tmp/MERGED-1505123141/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-fh	2024-08-22 05:53:24.702280334 -0400
      +++ /tmp/LIVE-676221210/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-fh	2024-08-22 05:53:24.702280334 -0400
      @@ -7,7 +7,11 @@
         deviceType: vfio-pci
         isRdma: false
         nicSelector:
      -    pfNames: null
      +    deviceID: "1593"
      +    pfNames: []
      +    rootDevices:
      +    - 0000:ca:00.2
      +    vendor: "8086"
         nodeSelector:
           node-role.kubernetes.io/master: ""
         numVfs: 8
      
      Differences found in CR: sriovnetwork.openshift.io/v1_SriovNetworkNodePolicy_openshift-sriov-network-operator_sriov-nnp-du-mh, Compared To Reference CR: required/sriov-operator/SriovNetworkNodePolicy.yaml
      diff -u -N /tmp/MERGED-566815213/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-mh /tmp/LIVE-967671406/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-mh
      --- /tmp/MERGED-566815213/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-mh	2024-08-22 05:53:24.704280372 -0400
      +++ /tmp/LIVE-967671406/sriovnetwork-openshift-io-v1_sriovnetworknodepolicy_openshift-sriov-network-operator_sriov-nnp-du-mh	2024-08-22 05:53:24.704280372 -0400
      @@ -7,7 +7,11 @@
         deviceType: vfio-pci
         isRdma: false
         nicSelector:
      -    pfNames: null
      +    deviceID: "1593"
      +    pfNames: []
      +    rootDevices:
      +    - 0000:ca:00.3
      +    vendor: "8086"
         nodeSelector:
           node-role.kubernetes.io/master: ""
         numVfs: 8
          

      Expected results:

      These differences in the SriovNetworkNodePolicy should be expected and not counted as differences against the reference
          

              jramsay1@redhat.com Jim Ramsay
              jramsay1@redhat.com Jim Ramsay
              Yang Liu Yang Liu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: