| Starting a task to upgrade the puppet-agent on windows hosts with relatively high load results in the winrm task failing with the message "timed out waiting for status response from <host>". 
The task is basically the command "choco upgrade puppet-agent". This task completes ok on a number of hosts (seems like it's mostly ones with the lowest average load) but about 115 out of 250 hosts show the result pictured above, when checked on, the install completes just fine when manually running "choco upgrade puppet-agent" doing it. From the chocolatey logs, all the clients failing to complete the task seem to have no trouble continuing the installation without an active winrm session, until they have to stop/start a service, at which point they fail (and leave the system without an active puppet-agent or pxp-service, but that's not what this ticket is about). Doing some digging, there seems to be no method within puppet to set an inactivity timeout for a winrm session at the moment. Doing more digging, it seems there's a windows registry key related to a winrm inactivity timeout: https://www.windows-security.org/a8984e09959b7cda375457a176edfee6/specify-idle-timeout And, it seems it is possible to set this activity timeout as the initiating party when connecting, which seems to happen here:
https://docs.microsoft.com/en-us/windows/win32/winrm/session-timeout#examples Is a configurable inactivity timeout something that could be implemented? |
