Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-9712

Dev Spaces operator not functional in IPv6 single stack deployment

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of problem:

      The Dev Spaces operator is not functional in IPv6 single stack deployments. Specifically, the devspaces-dashboard pods remain in CrashLoopBackOff state due to the following TLS error:

      2025-12-01T22:28:53.048951936Z           Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: fc00. is not in the cert's altnames: DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, DNS:openshift, DNS:openshift.default, DNS:openshift.default.svc, DNS:openshift.default.svc.cluster.local, DNS:fc00:30::1, IP Address:FC00:30:0:0:0:0:0:1
      2025-12-01T22:28:53.048951936Z               at Object.checkServerIdentity (node:tls:316:12)
      2025-12-01T22:28:53.048951936Z               at TLSSocket.onConnectSecure (node:_tls_wrap:1687:27)
      2025-12-01T22:28:53.048951936Z               at TLSSocket.emit (node:events:524:28)
      2025-12-01T22:28:53.048951936Z               at TLSSocket._finishInit (node:_tls_wrap:1076:8)
      2025-12-01T22:28:53.048951936Z               at ssl.onhandshakedone (node:_tls_wrap:862:12)
       

       

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

       1. Deploy OpenShift 4.20.0 in an IPv6 single-stack environment

      2. Install the Dev Spaces operator. In our environment, we installed:

      oc get csv
      NAME                            DISPLAY                        VERSION   REPLACES                        PHASE
      devspacesoperator.v3.24.0       Red Hat OpenShift Dev Spaces   3.24.0    devspacesoperator.v3.23.0       Succeeded
      devworkspace-operator.v0.37.0   DevWorkspace Operator          0.37.0    devworkspace-operator.v0.36.0   Succeeded
       

      Actual results:

      The devspaces-dashboard pods remain in CLBO status

      oc get pods -n openshift-operators | grep devspaces-dashboard
      devspaces-dashboard-9d45c475-w96wd                 0/1     CrashLoopBackOff   22         1h
      devspaces-dashboard-b85f54965-mh6wf                0/1     CrashLoopBackOff   22         1h
       

      Expected results:

      The devspaces-dashboard pods start normally

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      2025-12-01T22:28:53.048951936Z         "subjectaltname": "DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, DNS:openshift, DNS:openshift.default, DNS:openshift.default.svc, DNS:openshift.default.svc.cluster.local, DNS:fc00:30::1, IP Address:FC00:30:0:0:0:0:0:1",
      2025-12-01T22:28:53.048951936Z         "valid_from": "Nov 29 19:33:07 2025 GMT",
      2025-12-01T22:28:53.048951936Z         "valid_to": "Dec 29 19:33:08 2025 GMT"
      2025-12-01T22:28:53.048951936Z       },
      2025-12-01T22:28:53.048951936Z       "code": "ERR_TLS_CERT_ALTNAME_INVALID",
      2025-12-01T22:28:53.048951936Z       "host": "fc00",
      2025-12-01T22:28:53.048951936Z       "message": "Hostname/IP does not match certificate's altnames: Host: fc00. is not in the cert's altnames: DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, DNS:openshift, DNS:openshift.default, DNS:openshift.default.svc, DNS:openshift.default.svc.cluster.local, DNS:fc00:30::1, IP Address:FC00:30:0:0:0:0:0:1",
      2025-12-01T22:28:53.048951936Z       "reason": "Host: fc00. is not in the cert's altnames: DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, DNS:openshift, DNS:openshift.default, DNS:openshift.default.svc, DNS:openshift.default.svc.cluster.local, DNS:fc00:30::1, IP Address:FC00:30:0:0:0:0:0:1",
      2025-12-01T22:28:53.048951936Z       "stack":
      2025-12-01T22:28:53.048951936Z           Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: fc00. is not in the cert's altnames: DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, DNS:openshift, DNS:openshift.default, DNS:openshift.default.svc, DNS:openshift.default.svc.cluster.local, DNS:fc00:30::1, IP Address:FC00:30:0:0:0:0:0:1
      2025-12-01T22:28:53.048951936Z               at Object.checkServerIdentity (node:tls:316:12)
      2025-12-01T22:28:53.048951936Z               at TLSSocket.onConnectSecure (node:_tls_wrap:1687:27)
      2025-12-01T22:28:53.048951936Z               at TLSSocket.emit (node:events:524:28)
      2025-12-01T22:28:53.048951936Z               at TLSSocket._finishInit (node:_tls_wrap:1076:8)
      2025-12-01T22:28:53.048951936Z               at ssl.onhandshakedone (node:_tls_wrap:862:12)
      2025-12-01T22:28:53.048951936Z       "type": "Error"
      2025-12-01T22:28:53.048951936Z     }
       

       

              vsvydenk Valerii Svydenko
              rhn-support-jdelaros Jose De la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: