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

nfd operator not able to upgrade from 4.14 to 4.15 with message "error validating existing CRs against new CRD''s schema"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.14, 4.15.0
    • None
    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Not able to upgrade the nfd operator to the latest version i.e. 4.14 to 4.15 because of below error and the csv is in pending state:
      and sub having below status:
        - lastTransitionTime: "2025-02-05T19:18:24Z"
          message: 'error validating existing CRs against new CRD''s schema for "noderesourcetopologies.topology.node.k8s.io":
            error validating topology.node.k8s.io/v1alpha1, Kind=NodeResourceTopology "master.node.name.com":
            updated validation is too restrictive: [].topologyPolicies: Required value'
          reason: InstallComponentFailed
          status: "True"
          type: InstallPlanFailed

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

          4.14 -> 4.14

      How reproducible:

          100 %

      Steps to Reproduce:

      1. Installed OCP v4.14.37 
      2. Operator to install : 
         i. numaresources-operator.v4.14.3 with CR's as in the doc [1] 
         ii. nfd 4.14.0-202408260910 
      3. Upgrade the cluster to 4.15.44 
      4. Upgrade the numa to 4.15 
      5. Upgrade the nfd to 4.15.x versions 
      
      Note: Whether the IP was set to Auto or manual or upgrade in any order the issue was reproduced   
      
      [1]https://docs.redhat.com/en/documentation/openshift_container_platform/4.14/html/scalability_and_performance/cnf-numa-aware-scheduling#cnf-scheduling-numa-aware-workloads_numa-aware   

      Actual results:

          The CSV is in pending state

      Expected results:

          Installation should go seamlessly

      Additional info:

      Steps to Reproduce the issue:
      
      Workaround for the issue:
      - Deleted the pending CSV, sub and IP of the NFD
      - installed the nfd operator and kept the Install Plan approval as manual
      - then ran the below command to patch the crd before approving the IP
      ~~~
      $ oc patch crd noderesourcetopologies.topology.node.k8s.io --type='json' -p='[{"op": "replace", "path": "/spec/versions/0/served", "value": false}]'
      $ oc patch crd noderesourcetopologies.topology.node.k8s.io --type='json' -p='[{"op": "replace", "path": "/spec/versions/1/served", "value": false}]'
      ~~~
      - Approving the Install Plan the installation progressed ahead

       

              yshnaidm Yevgeny Shnaidman
              rhn-support-gmahto Gagan Mahto
              Guy Gordani Guy Gordani
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: