-
Bug
-
Resolution: Unresolved
-
Major
-
Windows Server 2019 (OS Build 17763.678)
Tool installation on a Windows node fails for some reason at this rename:
Unpacking [https://nodejs.org/dist/v10.16.3/node-v10.16.3-win-x64.zip] to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10 on devops-test3-vm java.io.IOException: Failed to rename C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64 to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64.__rename at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2171) at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2159) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Finished: FAILURE
Config:
[JENKINS-59867] NodeJS tool installation fails on Windows Server 2019
nfalco I'd be happy to do some investigation and run some samples if you can point me in the right direction. Neither maven nor groovy auto-installs have this issue so the installation must be done differently (ie not using MoveAllChildrenTo?)
My guess was something to do with the old MAX_PATH limit, but if it's only Windows 2019 that's more odd.
Frank Racis
added a comment - The "ant" install is also failing on Windows 2019.
Here's the offending operation in Process Monitor:
High Resolution Date & Time: 6/10/2022 1:47:21.1515478 PM Event Class: File System Operation: SetRenameInformationFile Result: ACCESS DENIED Path: D:\junk\tools\hudson.tasks.Ant_AntInstallation\ant-default\apache-ant-1.9.4 TID: 13788 Duration: 0.0004141 ReplaceIfExists: False FileName: D:\junk\tools\hudson.tasks.Ant_AntInstallation\ant-default\apache-ant-1.9.4.__rename
That whole tree is set to Users/Full Control so an ACL issue is unlikely.
Frank Racis
added a comment - The "ant" install is also failing on Windows 2019.
Here's the offending operation in Process Monitor:
High Resolution Date & Time: 6/10/2022 1:47:21.1515478 PM
Event Class : File System
Operation: SetRenameInformationFile
Result: ACCESS DENIED
Path: D:\junk\tools\hudson.tasks.Ant_AntInstallation\ant- default \apache-ant-1.9.4
TID: 13788
Duration: 0.0004141
ReplaceIfExists: False
FileName: D:\junk\tools\hudson.tasks.Ant_AntInstallation\ant- default \apache-ant-1.9.4.__rename
That whole tree is set to Users/Full Control so an ACL issue is unlikely.
I can confirm that this also happens exactly this way with nodejs 7, and only on Windows Server 2019 slaves. This does not happen on 2008, 2012, 2016 or Windows 10 (I have a matrix job with all of the above).
Deleting tools\jenkins.plugins.nodejs.tools.NodeJSInstallation did not help.
Environment: