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

[4.10] [OVN]Sometimes after reboot egress node, egress IP cannot be applied anymore.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • None
    • 4.12, 4.11, 4.10
    • None
    • SDN Sprint 230
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      [OVN][OSP] After reboot egress node, egress IP cannot be applied anymore.
      
      

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

      4.12.0-0.nightly-2022-11-07-181244
      
      

      How reproducible:

      Frequently happened in automation. But didn't reproduce it in manual.
      
      

      Steps to Reproduce:

      1. Label one node as egress node
      
      2.
      Config one egressIP object
      STEP: Check  one EgressIP assigned in the object.
      
      Nov  8 15:28:23.591: INFO: egressIPStatus: [{"egressIP":"192.168.54.72","node":"huirwang-1108c-pg2mt-worker-0-2fn6q"}]
      
      3.
      Reboot the node, wait for the node ready.
      
      
      

      Actual results:

      EgressIP cannot be applied anymore. Waited more than 1 hour.
       oc get egressip
      NAME             EGRESSIPS       ASSIGNED NODE   ASSIGNED EGRESSIPS
      egressip-47031   192.168.54.72    
      

      Expected results:

      The egressIP should be applied correctly.
      

      Additional info:

      
      Some logs
      E1108 07:29:41.849149       1 egressip.go:1635] No assignable nodes found for EgressIP: egressip-47031 and requested IPs: [192.168.54.72]
      I1108 07:29:41.849288       1 event.go:285] Event(v1.ObjectReference{Kind:"EgressIP", Namespace:"", Name:"egressip-47031", UID:"", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Warning' reason: 'NoMatchingNodeFound' no assignable nodes for EgressIP: egressip-47031, please tag at least one node with label: k8s.ovn.org/egress-assignable
      
      
      W1108 07:33:37.401149       1 egressip_healthcheck.go:162] Could not connect to huirwang-1108c-pg2mt-worker-0-2fn6q (10.131.0.2:9107): context deadline exceeded
      I1108 07:33:37.401348       1 master.go:1364] Adding or Updating Node "huirwang-1108c-pg2mt-worker-0-2fn6q"
      I1108 07:33:37.437465       1 egressip_healthcheck.go:168] Connected to huirwang-1108c-pg2mt-worker-0-2fn6q (10.131.0.2:9107)
      

      After this log, seems like no logs related to "192.168.54.72" happened.

      Attachments

        Issue Links

          Activity

            People

              ffernand@redhat.com Flavio Fernandes (Inactive)
              huirwang Huiran Wang
              Huiran Wang Huiran Wang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: