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

Single-stack IPv6 installation fails to run cluster api system

XMLWordPrintable

    • +
    • Important
    • None
    • ShiftStack Sprint 265, ShiftStack Sprint 266
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

         The OpenShift installer fails to create a cluster on an OpenStack Single-stack IPv6 environment - failed to run cluster api system

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

      Installer version:
       openshift-install version
      openshift-install 4.18.0-rc.3
      built from commit 0f87b38910a84cfe3243fb878436bc052afc3187
      release image registry.ci.openshift.org/ocp/release@sha256:668c92b06279cb5c7a2a692860b297eeb9013af10d49d2095f2c3fe9ad02baaa
      WARNING Release Image Architecture not detected. Release Image Architecture is unknown
      release architecture unknown
      default architecture amd64

      RHOSO version:

      [zuul@controller-0 ~]$ oc get openstackversions.core.openstack.org
      NAME           TARGET VERSION            AVAILABLE VERSION         DEPLOYED VERSION
      controlplane   18.0.4-trunk-20241112.1   18.0.4-trunk-20241112.1   18.0.4-trunk-20241112.1 

      How reproducible:

          Always

      Steps to Reproduce:

          1. Prepare openstack infra for openshift installation with Single-stack IPv6 (see the install-config.yaml below)
          2. openshift-install create cluster

      install-config.yaml:

       

      apiVersion: v1
      baseDomain: "shiftstack.local"
      controlPlane:
        name: master
        platform:
          openstack:
            type: "master"
        replicas: 3
      compute:
      - name: worker
        platform:
          openstack:
            type: "worker"
        replicas: 2
      metadata:
        name: "ostest"
      networking:
        clusterNetworks:
        - cidr: fd01::/48
          hostPrefix: 64
        machineNetwork:
          - cidr: "fd2e:6f44:5dd8:c956::/64"
        serviceNetwork:
          - fd02::/112
        networkType: "OVNKubernetes"
      platform:
        openstack:
          cloud:            "shiftstack"
          region:           "regionOne"
          apiVIPs: ["fd2e:6f44:5dd8:c956::5"]
          ingressVIPs: ["fd2e:6f44:5dd8:c956::7"]
          controlPlanePort:
            fixedIPs:
              - subnet:
                  name: "subnet-ssipv6"
      pullSecret: <omitted> 
      sshKey:     <omitted>

       

       

      Actual results:

      The openshift-install fails to start the controlplane - kube-apiserver:

      INFO Started local control plane with envtest
      E0109 13:17:36.425059   30979 server.go:328] "unable to start the controlplane" err="timeout waiting for process kube-apiserver to start successfully (it may have failed to start, or stopped unexpectedly before becoming ready)" logger="controller-runtime.test-env" tries=0
      E0109 13:17:38.365005   30979 server.go:328] "unable to start the controlplane" err="timeout waiting for process kube-apiserver to start successfully (it may have failed to start, or stopped unexpectedly before becoming ready)" logger="controller-runtime.test-env" tries=1
      E0109 13:17:40.142385   30979 server.go:328] "unable to start the controlplane" err="timeout waiting for process kube-apiserver to start successfully (it may have failed to start, or stopped unexpectedly before becoming ready)" logger="controller-runtime.test-env" tries=2
      E0109 13:17:41.947245   30979 server.go:328] "unable to start the controlplane" err="timeout waiting for process kube-apiserver to start successfully (it may have failed to start, or stopped unexpectedly before becoming ready)" logger="controller-runtime.test-env" tries=3
      E0109 13:17:43.761197   30979 server.go:328] "unable to start the controlplane" err="timeout waiting for process kube-apiserver to start successfully (it may have failed to start, or stopped unexpectedly before becoming ready)" logger="controller-runtime.test-env" tries=4
      DEBUG Collecting applied cluster api manifests...
      ERROR failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to run cluster api system: failed to run local control plane: unable to start control plane itself: failed to start the controlplane. retried 5 times: timeout waiting for process kube-apiserver to start successfully (it may have failed to start, or stopped unexpectedly before becoming ready)    

       

      Additional info:

      After the openshift-install failure, we observe that the kube-apiserver attempts to find service IPv4, even though our environment exclusively supports IPv6:

          $ cat ostest/.clusterapi_output/kube-apiserver.log
      I0109 13:17:36.402549   31041 options.go:228] external host was not specified, using fd01:0:0:3::97
      E0109 13:17:36.403397   31041 run.go:72] "command failed" err="service IP family \"10.0.0.0/24\" must match public address family \"fd01:0:0:3::97\""
      I0109 13:17:38.351573   31096 options.go:228] external host was not specified, using fd01:0:0:3::97
      E0109 13:17:38.352116   31096 run.go:72] "command failed" err="service IP family \"10.0.0.0/24\" must match public address family \"fd01:0:0:3::97\""
      I0109 13:17:40.129451   31147 options.go:228] external host was not specified, using fd01:0:0:3::97
      E0109 13:17:40.130026   31147 run.go:72] "command failed" err="service IP family \"10.0.0.0/24\" must match public address family \"fd01:0:0:3::97\""
      I0109 13:17:41.517490   31203 options.go:228] external host was not specified, using fd01:0:0:3::97
      E0109 13:17:41.518118   31203 run.go:72] "command failed" err="service IP family \"10.0.0.0/24\" must match public address family \"fd01:0:0:3::97\""
      I0109 13:17:43.750048   31258 options.go:228] external host was not specified, using fd01:0:0:3::97
      E0109 13:17:43.750649   31258 run.go:72] "command failed" err="service IP family \"10.0.0.0/24\" must match public address family \"fd01:0:0:3::97\""

       

      $ ip addr show
      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          inet 127.0.0.1/8 scope host lo
             valid_lft forever preferred_lft forever
          inet6 ::1/128 scope host
             valid_lft forever preferred_lft forever
      2: eth0@if174: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP group default
          link/ether 0a:58:19:b4:10:b3 brd ff:ff:ff:ff:ff:ff link-netnsid 0
          inet6 fd01:0:0:3::97/64 scope global
             valid_lft forever preferred_lft forever
          inet6 fe80::858:19ff:feb4:10b3/64 scope link
             valid_lft forever preferred_lft forever 

              mdemaced Maysa De Macedo Souza
              rhn-support-imatza Itay Matza
              Itshak Brown Itshak Brown
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: