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

IPI Baremetal Master Node in DualStack getting fd69:: address randomly, OVN CrashLoopBackOff

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • None
    • 4.12.0
    • Networking / ovn-kubernetes
    • None
    • Critical
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      After IPI installing a 3-node Hub Cluster, and converting them to dual stack, fd69::/125 address is seen in the Baremetal br-ex interface

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

      4.12.0

      How reproducible:

      Ranodmly reproduced and this IP is assigned in one of the 3 master hub cluster nodes

      Steps to Reproduce:

      1. IPI install 4.12.0
2. Use the Convert from IPv4/IPv6 dual stack procedure. 
3.

      Actual results:

      Check for the IP fd69::/125 in the br-ex interface

      OVN CrashLoopBackOff

      Expected results:

      The IP is a internal OVNKUBE IP, and it should not appear on the interface.

      fd69::2/125 should be present on br-ex, but make sure fd69::2 does not :

      1. show up as an address in the node Status.Addresses list at all
      2. exist in any Node object annotations

      Additional info:

      This is one of the issues in IPv6 that is discovered, the other issue is linked here as well.

      Attachments

        1. fd69_on_br-ex.png
          fd69_on_br-ex.png
          98 kB
        2. image-2023-01-23-14-46-28-365.png
          image-2023-01-23-14-46-28-365.png
          80 kB
        3. journalctl-ocp6504.txt
          15.54 MB
        4. oc-describe-of-crashing-pod.png
          oc-describe-of-crashing-pod.png
          115 kB
        5. ovnkube-pods-crashing.png
          ovnkube-pods-crashing.png
          30 kB

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-7223 [4.12] IPI Baremetal Master Node in DualStack getting fd69:: address randomly, OVN CrashLoopBackOff

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-7223 [4.12] IPI Baremetal Master Node in DualStack getting fd69:: address randomly, OVN CrashLoopBackOff

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-12799 OCP 4.12.x Upgrade Failure: OVN-KUBE-POD Crashes

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          Web Link node: don't consider internal masquerade addresses as node IP addresses

          Web Link Upstream PR

          Activity

            People

              dcbw@redhat.com Dan Williams (Inactive)
              mjanardh@redhat.com Mohan Raj Janardhan
              Ross Brattain Ross Brattain
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: