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

[CAPI] no windows-user-data in openshift-cluster-api namespace and windows machine stuck in Pending

XMLWordPrintable

    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

         [CAPI] no windows-user-data in openshift-cluster-api namespace and windows machine stuck in Pending

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

          4.17.0-0.nightly-2024-08-09-031511

      How reproducible:

          always

      Steps to Reproduce:

          1.Create a techpreview cluster with wmco installed, we use automated template, ipi-on-aws/versioned-installer-techpreview-ovn-winc-ci
      
      liuhuali@Lius-MacBook-Pro huali-test % oc get clusterversion
      NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
      version   4.17.0-0.nightly-2024-08-09-031511   True        False         35m     Cluster version is 4.17.0-0.nightly-2024-08-09-031511
      liuhuali@Lius-MacBook-Pro huali-test % oc get machine
      NAME                                                  PHASE     TYPE         REGION      ZONE         AGE
      huliu-aws813a-4j8zp-master-0                          Running   m6i.xlarge   us-east-2   us-east-2a   57m
      huliu-aws813a-4j8zp-master-1                          Running   m6i.xlarge   us-east-2   us-east-2b   57m
      huliu-aws813a-4j8zp-master-2                          Running   m6i.xlarge   us-east-2   us-east-2c   57m
      huliu-aws813a-4j8zp-windows-worker-us-east-2a-9m8gv   Running   m5a.large    us-east-2   us-east-2a   24m
      huliu-aws813a-4j8zp-windows-worker-us-east-2a-f4wwf   Running   m5a.large    us-east-2   us-east-2a   24m
      huliu-aws813a-4j8zp-worker-us-east-2a-4vg74           Running   m6i.xlarge   us-east-2   us-east-2a   54m
      huliu-aws813a-4j8zp-worker-us-east-2b-x9ddz           Running   m6i.xlarge   us-east-2   us-east-2b   54m
      huliu-aws813a-4j8zp-worker-us-east-2c-vrcbc           Running   m6i.xlarge   us-east-2   us-east-2c   54m
      
          2.Create cluster, awsmachinetemplate, and capi machine set
      liuhuali@Lius-MacBook-Pro huali-test % oc create -f cluster618.yaml 
      cluster.cluster.x-k8s.io/huliu-aws813a-4j8zp created
      liuhuali@Lius-MacBook-Pro huali-test % cat cluster618.yaml 
      apiVersion: cluster.x-k8s.io/v1beta1
      kind: Cluster
      metadata:
        name: huliu-aws813a-4j8zp
        namespace: openshift-cluster-api
      spec:
        infrastructureRef:
          apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
          kind: AWSCluster
          name: huliu-aws813a-4j8zp
          namespace: openshift-cluster-api 
      liuhuali@Lius-MacBook-Pro huali-test % oc create -f  awsmachinetemplate618.yaml 
      awsmachinetemplate.infrastructure.cluster.x-k8s.io/aws-machinetemplate created
      liuhuali@Lius-MacBook-Pro huali-test % cat awsmachinetemplate618.yaml 
      apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
      kind: AWSMachineTemplate
      metadata:
        name: aws-machinetemplate
        namespace: openshift-cluster-api
      spec:
        template:
          spec:
            uncompressedUserData: true
            iamInstanceProfile: huliu-aws813a-4j8zp-worker-profile
            instanceType: m5a.large
            failureDomain: us-east-2a
            ignition:
              storageType: UnencryptedUserData
              version: "3.2"
            ami:
              id: ami-0ec361a79fdf929d3
            additionalSecurityGroups:
            - filters:
              - name: tag:Name
                values:
                - huliu-aws813a-4j8zp-node
            - filters:
              - name: tag:Name
                values:
                - huliu-aws813a-4j8zp-lb
            subnet:
              filters:
              - name: tag:Name
                values:
                - huliu-aws813a-4j8zp-subnet-private-us-east-2a
      liuhuali@Lius-MacBook-Pro huali-test % oc create -f machineset618.yaml 
      machineset.cluster.x-k8s.io/capi-machineset-test1 created
      liuhuali@Lius-MacBook-Pro huali-test % cat machineset618.yaml
      apiVersion: cluster.x-k8s.io/v1beta1
      kind: MachineSet
      metadata:
        name: capi-machineset-test1
        namespace: openshift-cluster-api
      spec:
        clusterName: huliu-aws813a-4j8zp
        replicas: 1
        selector:
          matchLabels:
            machine.openshift.io/cluster-api-cluster: huliu-aws813a-4j8zp
        template:
          metadata:
            labels:
              machine.openshift.io/cluster-api-cluster: huliu-aws813a-4j8zp
          spec:
            bootstrap:
               dataSecretName: windows-user-data
            clusterName: huliu-aws813a-4j8zp
            infrastructureRef:
              apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
              kind: AWSMachineTemplate
              name: aws-machinetemplate
      
          3.the windows machine stuck in Pending
      liuhuali@Lius-MacBook-Pro huali-test % oc get machine.c                                
      NAME                          CLUSTER               NODENAME   PROVIDERID   PHASE     AGE   VERSION
      capi-machineset-test1-s5qr9   huliu-aws813a-4j8zp                           Pending   15m   
      
      liuhuali@Lius-MacBook-Pro huali-test % oc logs capa-controller-manager-b78bb49cc-qzczq 
      ...
      I0813 08:34:34.661561       1 awsmachine_controller.go:710] "Creating EC2 instance"
      E0813 08:34:34.661685       1 awsmachine_controller.go:529] "unable to create instance" err="failed to resolve userdata: failed to retrieve bootstrap data secret for AWSMachine openshift-cluster-api/capi-machineset-test1-s5qr9: Secret \"windows-user-data\" not found"
      E0813 08:34:34.662219       1 controller.go:329] "Reconciler error" err="failed to resolve userdata: failed to retrieve bootstrap data secret for AWSMachine openshift-cluster-api/capi-machineset-test1-s5qr9: Secret \"windows-user-data\" not found" controller="awsmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="AWSMachine" AWSMachine="openshift-cluster-api/capi-machineset-test1-s5qr9" namespace="openshift-cluster-api" name="capi-machineset-test1-s5qr9" reconcileID="a174e421-656c-4d8f-8919-f3d30912f068"    
      
      liuhuali@Lius-MacBook-Pro huali-test % oc get secret -n openshift-machine-api |grep user     
      master-user-data                                     Opaque                    2      5h19m
      master-user-data-managed                             Opaque                    2      5h17m
      windows-user-data                                    Opaque                    1      4h46m
      worker-user-data                                     Opaque                    2      5h19m
      worker-user-data-managed                             Opaque                    2      5h17m
      liuhuali@Lius-MacBook-Pro huali-test % oc get secret -n openshift-cluster-api |grep user
      worker-user-data                             Opaque                                2      5h17m
      liuhuali@Lius-MacBook-Pro huali-test %  

      Actual results:

          capi windows machine stuck in Pending

      Expected results:

           capi windows machine should get Running

      Additional info:

          

            joelspeed Joel Speed
            huliu@redhat.com Huali Liu
            Zhaohua Sun Zhaohua Sun
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: