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

hypershift deployment fails on disconnected- ipv6 deployment with ImageDigestMirrorSet

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • Done
    • Bug Fix
    • Hide
      * Previously, the IDMS or ICSP resources from the management cluster were processed without considering that a user might specify only the root registry name as a mirror or source for image replacement. As a consequence, any IDMS or ICSP entries that used only the root registry name did not work as expected. With this release, the mirror replacement logic now correctly handles cases where only the root registry name is provided. As a result, the issue no longer occurs, and the root registry mirror replacements are now supported. (link:https://issues.redhat.com/browse/OCPBUGS-55693[OCPBUGS-55693])
      Show
      * Previously, the IDMS or ICSP resources from the management cluster were processed without considering that a user might specify only the root registry name as a mirror or source for image replacement. As a consequence, any IDMS or ICSP entries that used only the root registry name did not work as expected. With this release, the mirror replacement logic now correctly handles cases where only the root registry name is provided. As a result, the issue no longer occurs, and the root registry mirror replacements are now supported. (link: https://issues.redhat.com/browse/OCPBUGS-55693 [ OCPBUGS-55693 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-54483. The following is the description of the original issue:
      —
      Description of problem:

      When trying to deploy hypershift on a disconnected- ipv6 deployment with ImageDigestMirrorSet, although the control plane is "Available", and "Installed", it dosn't show clusterOperators.

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

      [kni@ocp-edge119 ~]$ ~/hypershift_working/hypershift/bin/hcp version
Client Version: openshift/hypershift: 5d3ede17b74b36452402ab375b882e7f2f289884. Latest supported OCP: 4.17.0
Server Version: 5d3ede17b74b36452402ab375b882e7f2f289884
Server Supports OCP Versions: 4.17, 4.16, 4.15, 4.14
[kni@ocp-edge119 ~]$ oc version
Client Version: 4.17.20
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: 4.17.20
Kubernetes Version: v1.30.10
[kni@ocp-edge119 ~]$ 

      How reproducible:

          100%

      Steps to Reproduce:

          1.deploy a hub cluster with 3 master nodes disconnected ipv6 and idms
    2.deploy a MCE operator

(for step 1+2, I've used this job with cloned images https://jenkins-csb-kniqe-auto.dno.corp.redhat.com/job/Private_Folders/job/asher/job/factory-cluster-clone/27/)
    
    3. deploy hypershift with 2 workers on that hub cluster.
(for step 3, I've used : https://jenkins-csb-kniqe-auto.dno.corp.redhat.com/job/CI/job/job-runner/4878/)

      Actual results:

          Cluster is reported as Available & installed :
[kni@ocp-edge119 ~]$ oc wait --for=condition=Available=True hostedclusters -n clusters hosted-0
hostedcluster.hypershift.openshift.io/hosted-0 condition met
[kni@ocp-edge119 ~]$ oc get cd hosted-0 -n clusters-hosted-0 -o json | jq '.spec.installed'
true
[kni@ocp-edge119 ~]$ oc get hc -n clusters hosted-0
NAME       VERSION   KUBECONFIG                  PROGRESS   AVAILABLE   PROGRESSING   MESSAGE
hosted-0             hosted-0-admin-kubeconfig   Partial    True        False         The hosted control plane is available
[kni@ocp-edge119 ~]$ 

      there is no clusterOperator resource on the new cluster:
[kni@ocp-edge119 ~]$ oc get co -A --kubeconfig ~/clusterconfigs/hosted-0/auth/kubeconfig 
error: the server doesn't have a resource type "co"

      Expected results:

      cluster operators are up and running :
[kni@ocp-edge119 ~]$ oc get co -A --kubeconfig ~/clusterconfigs/hosted-1/auth/kubeconfig 
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
...  

      Additional info:

      Must gather: https://s3.upshift.redhat.com/DH-PROD-OCP-EDGE-QE-CI/ocp-spoke-assisted-operator-deploy/16356/index.html
      Failing CI profile :
https://jenkins-csb-kniqe-ci.dno.corp.redhat.com/job/CI/job/hypershift-agent-adding-nodepools-mce-2-7-ipv6-disconnected

       

       

              jparrill@redhat.com Juan Manuel Parrilla Madrid
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              He Liu He Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: