Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-70954

[Doc] CUDN example fails with "error validating data: apiVersion not set;"

XMLWordPrintable

    • Quality / Stability / Reliability
    • 1
    • False
    • Hide

      None

      Show
      None
    • True
    • None
    • CNV Doc Sprint 281
    • Low
    • None

      Description of problem:

      The CUDN creation based on example manifest fails with missing apiVersion.

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

      4.19

      How reproducible:

      Using a similar CUDN manifest file following the example in procedure step 1 in [1], the creation fails due to missing apiVersion provided.
      [1] https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html-single/virtualization/index#virt-creating-a-primary-cluster-udn_virt-connecting-vm-to-primary-udn

      Steps to Reproduce:

      1. create a  CUDN definition file following the example manifest in [1]
      2. oc apply --validate=true -f udn-cluster-udn.yaml
      3.
      

      Actual results:

      error: resource mapping not found for name: "udn-cluster-primary-l2" namespace: "" from "udn-cluster-udn.yaml": no matches for kind "ClusterUserDefinedNetwork" in version ""

      Expected results:

      clusteruserdefinednetwork.k8s.ovn.org/udn-cluster-primary-l2 created

      Additional info:

      The example manifest file should be enhanced with the apiVersion declaration: 
      apiVersion: k8s.ovn.org/v1

              abrennan@redhat.com Ashleigh Brennan
              matthiasmuench Matthias Muench
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: