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

References to ovnkube-control-plane should show two pods

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.15.0
    • Documentation / SDN
    • No
    • 2
    • OSDOCS Sprint 249
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when using the assisted installer, OVN-Kubernetes took a long time to bootstrap. This issue occurred because there were three `ovnkube-control-plane` nodes. The first two started up normally, however the third delayed delayed the installation time. The issue would only resolve after a timeout expiration; afterwards, installation would continue.
      +
      With this update, the third `ovnkube-control-plane` node has been removed. As a result, the installation time has been reduced. (link:https://issues.redhat.com/browse/OCPBUGS-29480[*OCPBUGS-29480*])
      Show
      * Previously, when using the assisted installer, OVN-Kubernetes took a long time to bootstrap. This issue occurred because there were three `ovnkube-control-plane` nodes. The first two started up normally, however the third delayed delayed the installation time. The issue would only resolve after a timeout expiration; afterwards, installation would continue. + With this update, the third `ovnkube-control-plane` node has been removed. As a result, the installation time has been reduced. (link: https://issues.redhat.com/browse/OCPBUGS-29480 [* OCPBUGS-29480 *])
    • Release Note Not Required
    • In Progress

      Description of problem:

          From 4.14 to 4.15, the ovnkube-control-plane deployment has scaled back from 3 pods to 2. The networking guide in 4.14 has many references to this pod and shows 3 pods in all the examples. That was correct for 4.14 but it should be 2 in 4.15.  Also, this paragraph needs to be changed:
      
      "The Kubernetes control plane nodes each contain an ovnkube-control-plane pod which does the central IP address management (IPAM) allocation for each node in the cluster. At any given time a single ovnkube-control-plane pod is the leader."
      
      Should say:
      "The Kubernetes control plane nodes contain two ovnkube-control-plane pods, on separate nodes, which does the central IP address management (IPAM) allocation for each node in the cluster. At any given time a single ovnkube-control-plane pod is the leader."

       

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

          4.15+

      How reproducible:

          100%

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

            rhn-support-stevsmit Steven Smith
            rhn-support-cfields Chris Fields
            Ross Brattain Ross Brattain
            Chris Fields
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: