Description of problem:

When changing internalJoinSubnet and internalTransitSwitchSubnet in day2(post installation).  the origin route in ovn router were not be removed. 

 

oc patch network.operator.openshift.io cluster --type='merge' -p='{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"ipv4":

{"internalJoinSubnet": "100.82.0.0/16"}

}}}}'

oc patch network.operator.openshift.io cluster --type='merge' -p='{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"ipv4":

{"internalTransitSwitchSubnet": "100.69.0.0/16"}

}}}}'

 

After changing and check the ovndb 

sh-5.1# ovn-nbctl lr-route-list ovn_cluster_router
IPv4 Routes
Route Table <main>:
               100.64.0.2                100.69.0.2 dst-ip ecmp  <----
               100.64.0.2                100.88.0.2 dst-ip ecmp   <----
               100.64.0.3                100.69.0.3 dst-ip ecmp <----
               100.64.0.3                100.88.0.3 dst-ip ecmp <----
               100.64.0.4                100.69.0.4 dst-ip ecmp <----
               100.64.0.4                100.88.0.4 dst-ip ecmp <----
               100.64.0.5                100.69.0.5 dst-ip ecmp <----
               100.64.0.5                100.88.0.5 dst-ip ecmp <----
               100.64.0.6                100.69.0.6 dst-ip ecmp <----
               100.64.0.6                100.88.0.6 dst-ip ecmp <----
               100.64.0.7                100.69.0.7 dst-ip ecmp <----
               100.64.0.7                100.88.0.7 dst-ip ecmp <----
               100.64.0.8                100.69.0.8 dst-ip ecmp <----
               100.64.0.8                100.88.0.8 dst-ip ecmp <----
               100.64.0.9                100.64.0.9 dst-ip
               100.82.0.2                100.69.0.2 dst-ip
               100.82.0.3                100.69.0.3 dst-ip
               100.82.0.4                100.69.0.4 dst-ip
               100.82.0.5                100.69.0.5 dst-ip
               100.82.0.6                100.69.0.6 dst-ip
               100.82.0.7                100.69.0.7 dst-ip
               100.82.0.8                100.69.0.8 dst-ip
               100.82.0.9                100.82.0.9 dst-ip
            10.128.0.0/23                100.69.0.2 dst-ip ecmp
            10.128.0.0/23                100.88.0.2 dst-ip ecmp  <----
            10.128.2.0/23                100.69.0.6 dst-ip ecmp
            10.128.2.0/23                100.88.0.6 dst-ip ecmp  <----
            10.129.0.0/23                100.69.0.3 dst-ip ecmp
            10.129.0.0/23                100.88.0.3 dst-ip ecmp  <----
            10.129.2.0/23                100.69.0.7 dst-ip ecmp
            10.129.2.0/23                100.88.0.7 dst-ip ecmp   <----
            10.130.0.0/23                100.69.0.4 dst-ip ecmp
            10.130.0.0/23                100.88.0.4 dst-ip ecmp  <----
            10.130.2.0/23                100.69.0.8 dst-ip ecmp
            10.130.2.0/23                100.88.0.8 dst-ip ecmp   <----
            10.131.0.0/23                100.69.0.5 dst-ip ecmp
            10.131.0.0/23                100.88.0.5 dst-ip ecmp   <----
            10.128.0.0/14                100.64.0.9 src-ip ecmp   <----
            10.128.0.0/14                100.82.0.9 src-ip ecmp

 

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

How reproducible:

Steps to Reproduce:

1.  setup cluster with ovn-k plugin

2.   change internalJoinSubnet and internalTransitSwitchSubnet in day2

oc patch network.operator.openshift.io cluster --type='merge' -p='{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"ipv4":

{"internalJoinSubnet": "100.82.0.0/16"}

}}}}'

oc patch network.operator.openshift.io cluster --type='merge' -p='{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"ipv4":

{"internalTransitSwitchSubnet": "100.69.0.0/16"}

}}}}'

3.

Actual results:

the old routes did not be removed from ovndb router

Expected results:

the old routes should be removed from ovndb router

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.
• Do presume that Engineering will access attachments through supportshell.
• Describe what each relevant 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.

• When showing the results from commands, include the entire command in the output.  
• 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, label with “sbr-untriaged”
• Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
• Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
• For guidance on using this template please see
  OCPBUGS Template Training for Networking  components