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

Over-ridding NMStateConfig causes omission of NMStateConfig as part of the generated CRs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.15
    • GitOps ZTP
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • No
    • None
    • Rejected
    • CNF RAN Sprint 248
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      If one tries to over-ride the NMStateConfig CR by providing a Node level crTemplate, the resulting CRs does not include the NMStateConfig CR because of logic flaw where we ignore that CR's generation if the user did not include the networking details in spec.clusters.nodes.NodeNetwork.Config and pec.clusters.nodes.NodeNetwork.Interfaces parts of the siteConfig.  The user did not include them because they are including it as part of the NMStateConfig over-ride.
      
      

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

          

      How reproducible:

          100%

      Steps to Reproduce:

          1. Remove the spec.clusters.nodes.NodeNetwork.Config and pec.clusters.nodes.NodeNetwork.Interfaces parts of the siteConfig and include crTemplate at the node level to over-ride the NMStateConfig CR
          2. run the siteConfigGenrator tool
          3. Observe the output
          

      Actual results:

          The NMStateConfig CR is missing from the generated CRs

      Expected results:

          The output CRs includes a NMStateConfig CR

      Additional info:

          

              dosman@redhat.com Dahir Osman
              dosman@redhat.com Dahir Osman
              None
              None
              Periyamaruthu Mohanraj Periyamaruthu Mohanraj
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: