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

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.13.z, 4.12.z, 4.14.0
    • Networking / ovn-kubernetes
    • None
    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      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.

            [OCPBUGS-13170] Routes are not restored to new vNIC by hybrid-overlay on Windows nodes

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Moderate: OpenShift Container Platform 4.13.1 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2023:3304

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Moderate: OpenShift Container Platform 4.13.1 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:3304

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in a merge request of openshift-winc-midstream / openshift-winc-midstream on branch rhaos-4.13-rhel-9_upstream_6b4140160919bd42f2939b1a1cb0d8d6:

            Updated US source to: 876908f Merge pull request #1615 from aravindhp/WINC-1037-r4.13

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of openshift-winc-midstream / openshift-winc-midstream on branch rhaos-4.13-rhel-9_ upstream _6b4140160919bd42f2939b1a1cb0d8d6 : Updated US source to: 876908f Merge pull request #1615 from aravindhp/ WINC-1037 -r4.13

            Anurag Saxena added a comment -

            Looks good on QE automation tests on 4.13.1. No issues found. Thanks

            Anurag Saxena added a comment - Looks good on QE automation tests on 4.13.1. No issues found. Thanks

              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

                Created:
                Updated:
                Resolved: