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

HostedControlPlane Nodeport service is not opened in a dualstack deployment

XMLWordPrintable

    • No
    • Hypershift Sprint 245
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, a node port failed to expose properly because the `ipFamilyPolicy` field was set to `SingleStack` for the `kube-apiserver` resource. With this update, if the `ipFamilyPolicy` is set to `PreferredDualStack`, node port is exposed properly. (link:https://issues.redhat.com/browse/OCPBUGS-23350[*OCPBUGS-23350*])
      Show
      * Previously, a node port failed to expose properly because the `ipFamilyPolicy` field was set to `SingleStack` for the `kube-apiserver` resource. With this update, if the `ipFamilyPolicy` is set to `PreferredDualStack`, node port is exposed properly. (link: https://issues.redhat.com/browse/OCPBUGS-23350 [* OCPBUGS-23350 *])
    • Bug Fix
    • Done

      Description of problem:

      After extensive debugging on HostedControlPlanes in dual stack mode, we have discovered that QE department has issues in dual stack environments. 
      
      In Hypershift/HostedControlPlane, we have an HAProxy in the dataplane (worker nodes of the HostedCluster). This HAProxy is unable to redirect calls to the KubeApiServer in the ControlPlane, attempts to connect using both protocols, IPv6 initially and then IPv4. The issue is that the HostedCluster is exposing services in NodePort mode, and it seems that the masterNodes of the management cluster are not opening these NodePorts in IPv6, only in IPv4.
      Even though the master node shows this trace with netstat:
      
      tcp6 9 0 :::32272 :::* LISTEN 6086/ovnkube
      
      It seems that it is only opening in IPv4, as it is not possible to connect to the API via IPv6 even locally. This only happens with dual stack; in the case of IPv4 and v6, it works correctly in single-stack mode.

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

      4.14.X
      4.15.X

      How reproducible:

      100%

      Steps to Reproduce:

      1. Deploy an Openshift management cluster in dual stack mode
      2. Deploy MCE 2.4
      3. Deploy a HostedCluster in dual stack mode 

      Actual results:

      - Many pods stuck in ContainerCreating state
      - The HostedCluster cannot be deployed, many COs blocked and clusterversion also stuck

      Expected results:

      HostedCluster deployment done

      Additional info:

      To reproduce the issue you could contact @jparrill or @Liangquan Li in slack, this will make things easier for the environment creation.

              jparrill@redhat.com Juan Manuel Parrilla Madrid
              jparrill@redhat.com Juan Manuel Parrilla Madrid
              Liangquan Li Liangquan Li
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: