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

[UDN pre-merge testing] "oc wait UserDefinedNetwork/<udn_name> -n <ns> --for condition=NetworkAllocationSucceeded=True" command would hang returnning no result

    • Moderate
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      Description of problem: After upgrade a cluster from non-UDN 4.17 image to 4.18 pre-merge EIP+UDN image, "oc wait UserDefinedNetwork/<udn_name>  -n <ns> --for condition=NetworkAllocationSucceeded=True" would hang returning no result

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

      How reproducible:

      Steps to Reproduce:

      1.  Build a cluster with non-UDN 4.17 nightly image

      2.  Upgrade the cluster to a 4.18 UDN image (I used a pre-merge image built from openshift/api#1997,  openshift/ovn-kubernetes@2333, that has EIP with UDN enabled)

      3. Create a new UDN, check if UDN is successfully applied with oc wait UserDefinedNetwork/<udn_name>  -n <ns> --for condition=NetworkAllocationSucceeded=True" 

      Actual results:  The command would hang, does not return any value, this only happens to cluster that was upgraded from non-UDN image to UDN image.   A freshly created cluster with UDN image directly does not have such a problem.

      Expected results: The command should return value to indicate the UDN is applied successfully or not.

       

              omergi@redhat.com Or Mergi
              jechen@redhat.com Jean Chen
              Jean Chen Jean Chen
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: