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

[AWS 2019] After deleting the BYOH node ConfigMap, the node is not being deconfigured and deleted as expected.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • None
    • 4.19
    • Windows Containers
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      After deleting the BYOH node ConfigMap, the node is not being deconfigured and deleted as expected.

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

      4.20.0-0.nightly-2025-10-15-110252
      10.20.0-e3c3dfe    

      How reproducible:

      100%

      Steps to Reproduce:

      1. Successfully create a 2019 BYOH node.
      2. Delete the BYOH node ConfigMap.
      
      
      

      Actual results:

          The BYOH node was neither deconfigured nor deleted after the ConfigMap was removed.
      

      Expected results:

          The BYOH node should be deconfigured and subsequently deleted after the ConfigMap is removed.
      

      Additional info:

      0. test case impacted: 42496
      
      1. Configmap status timeline:
      [2025-10-18 00:40:53] Starting to monitor ConfigMap windows-instances in namespace openshift-windows-machine-config-operator
      [2025-10-18 00:40:54] ✅ ConfigMap 'windows-instances   1      2m54s' CREATED in namespace 'openshift-windows-machine-config-operator'
      [2025-10-18 00:45:34] ❌ ConfigMap 'windows-instances   1      7m34s' DELETED from namespace 'openshift-windows-machine-config-operator'
      
      2. node status
       oc get no -o wide -l kubernetes.io/os=windows 
      NAME                                        STATUS                        ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION    CONTAINER-RUNTIME
      ip-10-0-10-60.us-east-2.compute.internal    Ready                         worker   90m   v1.33.3   10.0.10.60    <none>        Windows Server 2019 Datacenter   10.0.17763.7792   containerd://1.7.27
      ip-10-0-19-252.us-east-2.compute.internal   NotReady,SchedulingDisabled   worker   23m   v1.33.3   10.0.19.252   <none>        Windows Server 2019 Datacenter   10.0.17763.7792   containerd://1.7.27
      ip-10-0-31-222.us-east-2.compute.internal   Ready                         worker   94m   v1.33.3   10.0.31.222   <none>        Windows Server 2019 Datacenter   10.0.17763.7792   containerd://1.7.27
      
      3. wmco
      -0-10-60.us-east-2.compute.internal"}
      {"level":"info","ts":"2025-10-17T16:41:42Z","logger":"wc ip-10-0-19-252.us-east-2.compute.internal","msg":"configuring"}
      {"level":"info","ts":"2025-10-17T16:42:45Z","logger":"wc ip-10-0-19-252.us-east-2.compute.internal","msg":"rebooting instance"}
      {"level":"info","ts":"2025-10-17T16:43:07Z","logger":"wc ip-10-0-19-252.us-east-2.compute.internal","msg":"transferring files"}
      {"level":"info","ts":"2025-10-17T16:43:59Z","logger":"controllers.certificatesigningrequests","msg":"CSR approved","CSR":"csr-sxtgp"}
      {"level":"info","ts":"2025-10-17T16:44:02Z","logger":"controllers.certificatesigningrequests","msg":"CSR approved","CSR":"csr-9m2ch"}
      {"level":"info","ts":"2025-10-17T16:44:07Z","logger":"wc ip-10-0-19-252.us-east-2.compute.internal","msg":"configured","service":"windows-instance-config-daemon","args":"controller --windows-service --log-dir C:\\var\\log\\wicd --kubeconfig C:\\k\\wicd-kubeconfig --namespace openshift-windows-machine-config-operator --ca-bundle C:\\k\\ca-bundle.crt"}
      {"level":"info","ts":"2025-10-17T16:44:11Z","logger":"wc 10.0.19.252","msg":"rebooting instance"}
      {"level":"info","ts":"2025-10-17T16:45:15Z","logger":"controllers.certificatesigningrequests","msg":"CSR contents are invalid for approval by WMCO","CSR":"csr-dhqfn"}
      {"level":"info","ts":"2025-10-17T16:45:52Z","logger":"nc ip-10-0-19-252.us-east-2.compute.internal","msg":"instance has been configured as a worker node","version":"10.20.0-e3c3dfe"}
      {"level":"info","ts":"2025-10-17T16:46:52Z","logger":"controllers.configmap","msg":"processing","instances in":"windows-instances"}
      {"level":"info","ts":"2025-10-17T16:46:58Z","logger":"nc 10.0.19.252","msg":"deconfiguring"}
      {"level":"info","ts":"2025-10-17T16:46:59Z","logger":"wc 10.0.19.252","msg":"deconfigured","service":"windows-instance-config-daemon"}
      {"level":"info","ts":"2025-10-17T16:48:35Z","logger":"wc 10.0.19.252","msg":"rebooting instance"}
      {"level":"error","ts":"2025-10-17T16:58:33Z","msg":"Reconciler error","controller":"configmap","controllerGroup":"","controllerKind":"ConfigMap","ConfigMap":{"name":"windows-instances","namespace":"openshift-windows-machine-config-operator"},"namespace":"openshift-windows-machine-config-operator","name":"windows-instances","reconcileID":"8c064028-9b04-4dd4-a92e-d534cab77c5f","error":"error removing undesired nodes from cluster: unable to deconfigure instance with node ip-10-0-19-252.us-east-2.compute.internal: timeout waiting for windowsmachineconfig.openshift.io/reboot-required to be cleared: timed out waiting for the condition","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\t/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:353\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\t/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:300\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.1\n\t/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:202"}
      {"level":"info","ts":"2025-10-17T16:58:33Z","logger":"controllers.configmap","msg":"processing","instances in":"windows-instances"}
      {"level":"error","ts":"2025-10-17T17:05:06Z","msg":"Reconciler error","controller":"node","controllerGroup":"","controllerKind":"Node","Node":{"name":"ip-10-0-19-252.us-east-2.compute.internal"},"namespace":"","name":"ip-10-0-19-252.us-east-2.compute.internal","reconcileID":"8638394e-03ac-488d-bd79-879bbb0292ad","error":"full instance reboot failed: error reinitializing SSH connection after VM reboot: failed to reinitialize ssh client: unable to connect to Windows VM 10.0.19.252: timed out waiting for the condition","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\t/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:353\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\t/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:300\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.1\n\t/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:202"}
      
      
      
        

              team-winc Team WinC
              rhn-support-weinliu Weinan Liu
              None
              None
              Weinan Liu Weinan Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: