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

[release-4.12] The last egressIP in IP capacity cannot be applied correctly

XMLWordPrintable

    • Moderate
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      The last egressIP in IP capacity cannot be applied correctly
      
      

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

      4.11.0-0.nightly-2022-11-27-164248 
      
      

      How reproducible:

      Found this failure in automation case which used to pass
      
      

      Steps to Reproduce:

      In AWS, one worker node is with IP capacity "ipv4:14"
       $oc describe node ip-10-0-129-21.us-west-2.compute.internal | egrep -C 3 egress
      Annotations:        cloud.network.openshift.io/egress-ipconfig:
                            [{"interface":"eni-03820ba0eca427fbf","ifaddr":{"ipv4":"10.0.128.0/18"},"capacity":{"ipv4":14,"ipv6":15}}]
                          csi.volume.kubernetes.io/nodeid: {"ebs.csi.aws.com":"i-0cb3ae15bf3cffd9f"}
                          k8s.ovn.org/host-addresses: ["10.0.129.21"]
      

      1. Label above node as egress node
      2. Created 15 egressIP objects, each egressIP object with one egressIP.

      Actual results:

       13 egressIPs applied correctly , last one is in wrong status.
      % oc get egressip
      NAME                EGRESSIPS      ASSIGNED NODE                               ASSIGNED EGRESSIPS
      egressip-47208-0    10.0.135.200   ip-10-0-129-21.us-west-2.compute.internal   10.0.135.200
      egressip-47208-1    10.0.162.178   ip-10-0-129-21.us-west-2.compute.internal   10.0.162.178
      egressip-47208-10   10.0.144.46    ip-10-0-129-21.us-west-2.compute.internal   10.0.144.46
      egressip-47208-11   10.0.191.91    ip-10-0-129-21.us-west-2.compute.internal   10.0.191.91
      egressip-47208-12   10.0.133.215   ip-10-0-129-21.us-west-2.compute.internal   10.0.133.215
      egressip-47208-13   10.0.174.207   ip-10-0-129-21.us-west-2.compute.internal   10.0.174.207
      egressip-47208-14   10.0.176.224   ip-10-0-129-21.us-west-2.compute.internal   10.0.176.224
      egressip-47208-2    10.0.184.114   ip-10-0-129-21.us-west-2.compute.internal   10.0.184.114
      egressip-47208-3    10.0.167.224   ip-10-0-129-21.us-west-2.compute.internal   10.0.167.224
      egressip-47208-4    10.0.187.148   ip-10-0-129-21.us-west-2.compute.internal   10.0.187.148
      egressip-47208-5    10.0.184.109   ip-10-0-129-21.us-west-2.compute.internal   10.0.184.109
      egressip-47208-6    10.0.155.208                                               
      egressip-47208-7    10.0.134.13    ip-10-0-129-21.us-west-2.compute.internal   10.0.134.13
      egressip-47208-8    10.0.142.255   ip-10-0-129-21.us-west-2.compute.internal   10.0.142.255
      egressip-47208-9    10.0.170.197
      
      % oc get cloudprivateipconfig
      NAME           AGE
      10.0.133.215   113s
      10.0.134.13    113s
      10.0.135.200   113s
      10.0.142.255   113s
      10.0.144.46    113s
      10.0.155.208   113s
      10.0.162.178   113s
      10.0.167.224   113s
      10.0.174.207   113s
      10.0.176.224   113s
      10.0.184.109   113s
      10.0.184.114   113s
      10.0.187.148   113s
      10.0.191.91    113s
      
       oc get cloudprivateipconfig 10.0.155.208  -o yaml
      apiVersion: cloud.network.openshift.io/v1
      kind: CloudPrivateIPConfig
      metadata:
        annotations:
          k8s.ovn.org/egressip-owner-ref: egressip-47208-6
        creationTimestamp: "2022-11-28T09:13:47Z"
        finalizers:
        - cloudprivateipconfig.cloud.network.openshift.io/finalizer
        generation: 1
        name: 10.0.155.208
        resourceVersion: "72869"
        uid: 0143a07b-0a30-4de8-bfd7-589ed0c3d7dc
      spec:
        node: ip-10-0-129-21.us-west-2.compute.internal
      status:
        conditions:
        - lastTransitionTime: "2022-11-28T09:16:51Z"
          message: 'Error processing cloud assignment request, err: <nil>'
          observedGeneration: 1
          reason: CloudResponseError
          status: "False"
          type: Assigned
        node: ip-10-0-129-21.us-west-2.compute.internal
      
      

      Expected results:

      As IP capacity for this node is 14, so here should have 14 egress IP applied successfully. No cloudprivateipconfig IP in error status.
      
      
      

      Additional info:

      
      

            akaris@redhat.com Andreas Karis
            huirwang Huiran Wang
            Huiran Wang Huiran Wang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: