Windows nodes in Reconciling status

This document (000021254) is provided subject to the disclaimer at the end of this document.


Rancher 2.6 or 2.7
RKE2 custom or node-driver clusters with Windows worker nodes and Windows agents running as service.


Windows worker nodes are in Reconciling status, and the Rancher UI shows the message:

The rke2 agent logged an error similar to the following:
{failed to extract runtime image: open
                      C:\var\lib\rancher\rke2\data\v1.24.9-rke2r2-windows-amd64-bc939b774232\bin\containerd-shim-runhcs-v1.exe: The process cannot
                      access the file because it is being used by another process.}

The Windows rke2 service fails to start  due to some child previous processes needing to be finished properly from the previous rke2 service.


  1. Retrieve rke2 agent logs  
           1.1 Connect to the Windows worker node
           1.2 Start a Windows PowerShell
           1.3 Execute this command to retrieve the logs
Get-EventLog -LogName Application -Source 'rke2' -Newest 500 | format-table -Property TimeGenerated, ReplacementStrings -Wrap
 Output should be similiar to:  
10/26/2023 12:55:39 PM {failed to extract runtime image: open C:\var\lib\rancher\rke2\data\v1.24.9-rke2r2-windows-amd64
                       -bc939b774232\bin\containerd-shim-runhcs-v1.exe: The process cannot access the file because it
                       is being used by another process.}
10/26/2023 12:55:39 PM {Extracting file bin\containerd-shim-runhcs-v1.exe to C:\var\lib\rancher\rke2\data\v1.24.9-rke2r
10/26/2023 12:55:38 PM {Extracting file bin\calico.exe to
10/26/2023 12:55:34 PM {Starting rke2 agent v1.24.9+rke2r2 (2f4571a879954e1ea8d4560023eaf57c567df737)}
         2. Retrieve the Windows RKE2 service status     
The process is in a loop, trying to stop and start.
PS C:\> Get-Service rke2

Status   Name               DisplayName
------   ----               -----------
Start...  rke2               rke2

PS C:\> Get-Service rke2

Status   Name               DisplayName
------   ----               -----------
Stopped  rke2               rke2 
        3.  Stop the rke2 service
PS C:\> Stop-Service rke2
       4. Stop or kill all the child process
            4.1 List the processes
PS C:\>  Get-Process -Name calico-node,kubelet,containerd*,kube-proxy

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName
-------  ------    -----      -----     ------     --  -- -----------
    266      17    27196      40260   1,492.86   5552   0 calico-node
    186      11    17548      17132       5.39   4512   0 containerd-shim-runhcs-v1
          4.2 Kill all the processes listed on the previous command
PS C:\> Stop-Process -Name calico-node
PS C:\> Stop-Process -Name containerd-shim-runhcs-v1
           4.3 Ensure all of them are not running
       5. Start the rke2 service
PS C:\> Start-Service rke2

The rke2 agent service will be start without errors.



Additional Information


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000021254
  • Creation Date: 30-Oct-2023
  • Modified Date:16-Nov-2023

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center