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

apbexternalroute and egressfirewall status shows empty on hypershift hosted cluster[4.15]



    • No
    • SDN Sprint 248
    • 1
    • False
    • Hide


    • Release Note Not Required
    • In Progress


      Description of problem:

      apbexternalroute and egressfirewall status shows empty on hypershift hosted cluster

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


      How reproducible:


      Steps to Reproduce:

      1. setup hypershift, login hosted cluster
      % oc get node
      NAME                                         STATUS   ROLES    AGE    VERSION
      ip-10-0-128-55.us-east-2.compute.internal    Ready    worker   125m   v1.28.4+7aa0a74
      ip-10-0-129-197.us-east-2.compute.internal   Ready    worker   125m   v1.28.4+7aa0a74
      ip-10-0-135-106.us-east-2.compute.internal   Ready    worker   125m   v1.28.4+7aa0a74
      ip-10-0-140-89.us-east-2.compute.internal    Ready    worker   125m   v1.28.4+7aa0a74
      2. create new project test
      % oc new-project test
      3. create apbexternalroute and egressfirewall on hosted cluster
      apbexternalroute yaml file:
      apiVersion: k8s.ovn.org/v1
      kind: AdminPolicyBasedExternalRoute
        name: apbex-route-policy
              kubernetes.io/metadata.name: test
          - ip: ""
          - ip: ""
      % oc apply -f apbexroute.yaml 
      adminpolicybasedexternalroute.k8s.ovn.org/apbex-route-policy created
      egressfirewall yaml file:
      apiVersion: k8s.ovn.org/v1
      kind: EgressFirewall
        name: default
        - type: Allow
      % oc apply -f egressfw.yaml 
      egressfirewall.k8s.ovn.org/default created
      3. oc get apbexternalroute and oc get egressfirewall

      Actual results:

      The status show empty:
      % oc get apbexternalroute
      NAME                 LAST UPDATE   STATUS
      apbex-route-policy   49s                     <--- status is empty
      % oc describe apbexternalroute apbex-route-policy | tail -n 8
        Last Transition Time:  2023-12-19T06:54:17Z
          ip-10-0-135-106.us-east-2.compute.internal: configured external gateway IPs:,
          ip-10-0-129-197.us-east-2.compute.internal: configured external gateway IPs:,
          ip-10-0-128-55.us-east-2.compute.internal: configured external gateway IPs:,
          ip-10-0-140-89.us-east-2.compute.internal: configured external gateway IPs:,
      Events:  <none>
      % oc get egressfirewall
      default                           <--- status is empty 
      % oc describe egressfirewall default | tail -n 8
          Type:             Allow
          ip-10-0-129-197.us-east-2.compute.internal: EgressFirewall Rules applied
          ip-10-0-128-55.us-east-2.compute.internal: EgressFirewall Rules applied
          ip-10-0-140-89.us-east-2.compute.internal: EgressFirewall Rules applied
          ip-10-0-135-106.us-east-2.compute.internal: EgressFirewall Rules applied
      Events:  <none>

      Expected results:

      the status can be shown correctly

      Additional info:

      Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

      Affected Platforms:

      Is it an

      1. internal CI failure 
      2. customer issue / SD
      3. internal RedHat testing failure


      If it is an internal RedHat testing failure:

      • Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).


      If it is a CI failure:


      • Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
      • Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
      • Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
      • When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
      • If it's a connectivity issue,
      • What is the srcNode, srcIP and srcNamespace and srcPodName?
      • What is the dstNode, dstIP and dstNamespace and dstPodName?
      • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)


      If it is a customer / SD issue:


      • Provide enough information in the bug description that Engineering doesn't need to read the entire case history.
      • Don't presume that Engineering has access to Salesforce.
      • Please provide must-gather and sos-report with an exact link to the comment in the support case with the attachment.  The format should be: https://access.redhat.com/support/cases/#/case/<case number>/discussion?attachmentId=<attachment id>
      • Describe what each attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).  
      • Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
        • If the issue is in a customer namespace then provide a namespace inspect.
        • If it is a connectivity issue:
          • What is the srcNode, srcNamespace, srcPodName and srcPodIP?
          • What is the dstNode, dstNamespace, dstPodName and  dstPodIP?
          • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
          • Please provide the UTC timestamp networking outage window from must-gather
          • Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
        • If it is not a connectivity issue:
          • Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.
      • For OCPBUGS in which the issue has been identified, label with "sbr-triaged"
      • For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, labels with "sbr-untriaged"
      • Note: bugs that do not meet these minimum standards will be closed with label "SDN-Jira-template"


        Issue Links



              npinaeva@redhat.com Nadia Pinaeva
              rh-ee-qiowang Qiong Wang
              Qiong Wang Qiong Wang
              0 Vote for this issue
              4 Start watching this issue