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

Routes are not restored to new vNIC by hybrid-overlay on Windows nodes

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Undefined
    • None
    • 4.13.z, 4.12.z, 4.14.0
    • None
    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-12971. The following is the description of the original issue:

      Description of problem:

      hybrid-overlay on Windows nodes ignores existing non-persistent routes when creating the new vNIC. This becomes an issue especially on AWS where non-persistent routes are used for the local metadata server which is in turn used by the kubelet.
      How reproducible:{code:none}
      Always on Windows Server 2022 instances on AWS
      

      Steps to Reproduce:

      1. Bring up an hybrid-ovn OCP cluster on AWS
      2. Add a Windows Server 2022 Machine or BYOH instance
      

      Actual results:

      The Windows Server 2022 node goes to NotReady
      

      Expected results:

      The Windows Server 2022 node goes to Ready
      

      Additional info:

      While this problem shows up only on AWS, it can be an issue on other providers if customers are depending on non-persistent routes on Windows nodes in general.
      

      Attachments

        Issue Links

          Activity

            People

              jtanenba@redhat.com Jacob Tanenbaum
              openshift-crt-jira-prow OpenShift Prow Bot
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: