Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37332

java.io.IOException: Failed to rename during Plugin Update

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Windows
      Jenkins 2.17

      We are currently unable to update plugins in our jenkins installation, because this exception occurs:

      java.io.IOException: Failed to rename C:\Program Files (x86)\Jenkins\plugins\windows-slaves.jpi.tmp to C:\Program Files (x86)\Jenkins\plugins\windows-slaves.jpi
      at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952)
      at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178)
      at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653)
      at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848)
      at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624)
      at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
      at java.lang.Thread.run(Unknown Source)

      It doesn't seem to affect all plugins, but it also happends for the JUnit plugin.

          [JENKINS-37332] java.io.IOException: Failed to rename during Plugin Update

          Claus Näveke created issue -
          Keith Davis made changes -
          Comment [ Also, for Windows Slaves Plugin:

          java.io.IOException: Failed to rename C:\Jenkins\plugins\windows-slaves.jpi.tmp to C:\Jenkins\plugins\windows-slaves.jpi
          at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952)
          at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178)
          at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653)
          at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848)
          at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask.run(Unknown Source)
          at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
          at java.lang.Thread.run(Unknown Source) ]

          Martin Karing added a comment -

          I can confirm this issue happening for the windows slaves and the junit plug in.

          Martin Karing added a comment - I can confirm this issue happening for the windows slaves and the junit plug in.
          Claus Näveke made changes -
          Description Original: We are currently unable to update plugins in our jenkins installation, because this exception happens:

          java.io.IOException: Failed to rename C:\Program Files (x86)\Jenkins\plugins\windows-slaves.jpi.tmp to C:\Program Files (x86)\Jenkins\plugins\windows-slaves.jpi
          at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952)
          at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178)
          at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653)
          at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848)
          at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask.run(Unknown Source)
          at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
          at java.lang.Thread.run(Unknown Source)

          It doesn't seem to affect als plugin, but it also happend for the JUnit plugin.
          New: We are currently unable to update plugins in our jenkins installation, because this exception occurs:

          java.io.IOException: Failed to rename C:\Program Files (x86)\Jenkins\plugins\windows-slaves.jpi.tmp to C:\Program Files (x86)\Jenkins\plugins\windows-slaves.jpi
          at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952)
          at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178)
          at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653)
          at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848)
          at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask.run(Unknown Source)
          at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
          at java.lang.Thread.run(Unknown Source)

          It doesn't seem to affect all plugins, but it also happends for the JUnit plugin.

          Rob Cruz added a comment - - edited

          This is happening to me as well.

          Windows Slaves Plugin
          Failure -
          java.io.IOException: Failed to rename C:\Jenkins\plugins\junit.jpi.tmp to C:\Jenkins\plugins\junit.jpi
          at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952)
          at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178)
          at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653)
          at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848)
          at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask.run(Unknown Source)
          at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
          at java.lang.Thread.run(Unknown Source)

          JUnit Plugin
          Failure -
          java.io.IOException: Failed to rename C:\Jenkins\plugins\windows-slaves.jpi.tmp to C:\Jenkins\plugins\windows-slaves.jpi
          at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952)
          at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178)
          at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653)
          at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848)
          at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask.run(Unknown Source)
          at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
          at java.lang.Thread.run(Unknown Source)

          Rob Cruz added a comment - - edited This is happening to me as well. Windows Slaves Plugin Failure - java.io.IOException: Failed to rename C:\Jenkins\plugins\junit.jpi.tmp to C:\Jenkins\plugins\junit.jpi at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source) JUnit Plugin Failure - java.io.IOException: Failed to rename C:\Jenkins\plugins\windows-slaves.jpi.tmp to C:\Jenkins\plugins\windows-slaves.jpi at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1952) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1848) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source)

          Jeff Dafoe added a comment -

          On our install, it's happening for the plugins mentioned by others, as well as:
          LDAP Plugin
          Mailer Plugin
          Subversion Plug-in
          External Monitor Job Type Plugin
          Maven Integration plugin
          Javadoc Plugin
          Matrix Authorization Strategy Plugin
          OWASP Markup Formatter Plugin
          Matrix Project Plugin
          Ant Plugin
          PAM Authentication plugin

          Jeff Dafoe added a comment - On our install, it's happening for the plugins mentioned by others, as well as: LDAP Plugin Mailer Plugin Subversion Plug-in External Monitor Job Type Plugin Maven Integration plugin Javadoc Plugin Matrix Authorization Strategy Plugin OWASP Markup Formatter Plugin Matrix Project Plugin Ant Plugin PAM Authentication plugin

          Daniel Beck added a comment -

          All listed plugins are formerly bundled plugins.

          What circumstances do these issues appear in? Are you trying to update these plugins?

          Daniel Beck added a comment - All listed plugins are formerly bundled plugins. What circumstances do these issues appear in? Are you trying to update these plugins?

          Daniel Beck added a comment -

          Would be interesting to know if Jenkins has a lock on these plugin JPIs specifically, and not others, at the time the upgrade is attempted.

          Daniel Beck added a comment - Would be interesting to know if Jenkins has a lock on these plugin JPIs specifically, and not others, at the time the upgrade is attempted.

          Daniel Beck added a comment -

          Is this happening only since version 2.17, or did this issue occur earlier than that? What Jenkins versions were you running when you last tried to upgrade any plugin in Jeff's list?

          Daniel Beck added a comment - Is this happening only since version 2.17, or did this issue occur earlier than that? What Jenkins versions were you running when you last tried to upgrade any plugin in Jeff's list?

          Keith Davis added a comment - - edited

          I update Jenkins (first) and then any plugins every week. On 8/6, I updated to 2.17 and the all plugin updates available - no issues. On 8/11, there was no Jenkins update available and so I tried to update all plugins and these 2 failed. These are the plugins I updated on 8/11 and on 8/6.

          8/11:

          	Email Extension Plugin
          This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says.	2.47	2.46
          	Git Parameter Plug-In
          This plugin allows you to choose between Git tags or sha1 of your SCM repository so Git Plugin installed is required.	0.6.2	0.6.1
          	GitHub API Plugin
          This plugin is a library plugin used by other GitHub related plugins to share the same libraries. This plugin does not have any user visible feature by itself. There's no need to install this plugin manually, although you want to keep it up to date.	1.77	1.76
          	JUnit Plugin
          Allows JUnit-format test results to be published.	1.18	1.15
          	Pipeline: Groovy
          Pipeline execution engine based on continuation passing style transformation of Groovy scripts.	2.11	2.10
          	Pipeline: Input Step
          Adds the Pipeline step ‘input’ to wait for human input or approval.	2.1	2.0
          	Pipeline: Job
          Defines a new job type for pipelines and provides their generic user interface.	2.5	2.4
          	Pipeline: Shared Groovy Libraries
          Global shared library for Pipeline scripts.	2.2	2.1
          	Windows Slaves Plugin
          Allows you to connect to Windows machines and start slave agents on them.	1.2	1.1
          
          

          8/6:

          	Durable Task Plugin
          Library offering an extension point for processes which can run outside of Jenkins yet be monitored.	1.12	1.11
          	Email Extension Plugin
          This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says.	2.46	2.44
          	Git plugin
          This plugin allows use of Git as a build SCM, including repository browsers for several providers. A recent Git runtime is required (1.7.9 minimum, 1.8.x recommended). Interaction with the Git runtime is performed by the use of the [JENKINS:Git Client Plugin], which is only tested on official git client. Use exotic installations at your own risk.
          2.5.3	2.5.2
          	GitHub Organization Folder Plugin
          Pipeline-as-Code support for a whole GitHub organization. Scans all the branches & repositories in GitHub organization and build them via Jenkins pipelines automatically
          1.4	1.3
          	Pipeline: Basic Steps
          Commonly used steps for Pipelines.	2.1	2.0
          	Pipeline: Groovy
          Pipeline execution engine based on continuation passing style transformation of Groovy scripts.	2.10	2.9
          	Pipeline: Job
          Defines a new job type for pipelines and provides their generic user interface.	2.4	2.3
          	Pipeline: Nodes and Processes
          Pipeline steps locking agents and workspaces, and running external processes that may survive a Jenkins restart or slave reconnection.	2.4	2.3
          	Pipeline: REST API Plugin
          Provides a REST API to access pipeline and pipeline run data	1.7	1.6
          	Pipeline: Stage View Plugin
          Provides a swimlane view of the different stages in a pipeline.	1.7	1.6
          	Pipeline: Step API
          API for asynchronous build step primitive.	2.3	2.2
          	Structs Plugin
          Library plugin for DSL plugins that need concise names for Jenkins extensions	1.3	1.2
          
          
          

          Keith Davis added a comment - - edited I update Jenkins (first) and then any plugins every week. On 8/6, I updated to 2.17 and the all plugin updates available - no issues. On 8/11, there was no Jenkins update available and so I tried to update all plugins and these 2 failed. These are the plugins I updated on 8/11 and on 8/6. 8/11: Email Extension Plugin This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says. 2.47 2.46 Git Parameter Plug-In This plugin allows you to choose between Git tags or sha1 of your SCM repository so Git Plugin installed is required. 0.6.2 0.6.1 GitHub API Plugin This plugin is a library plugin used by other GitHub related plugins to share the same libraries. This plugin does not have any user visible feature by itself. There's no need to install this plugin manually, although you want to keep it up to date. 1.77 1.76 JUnit Plugin Allows JUnit-format test results to be published. 1.18 1.15 Pipeline: Groovy Pipeline execution engine based on continuation passing style transformation of Groovy scripts. 2.11 2.10 Pipeline: Input Step Adds the Pipeline step ‘input’ to wait for human input or approval. 2.1 2.0 Pipeline: Job Defines a new job type for pipelines and provides their generic user interface. 2.5 2.4 Pipeline: Shared Groovy Libraries Global shared library for Pipeline scripts. 2.2 2.1 Windows Slaves Plugin Allows you to connect to Windows machines and start slave agents on them. 1.2 1.1 8/6: Durable Task Plugin Library offering an extension point for processes which can run outside of Jenkins yet be monitored. 1.12 1.11 Email Extension Plugin This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says. 2.46 2.44 Git plugin This plugin allows use of Git as a build SCM, including repository browsers for several providers. A recent Git runtime is required (1.7.9 minimum, 1.8.x recommended). Interaction with the Git runtime is performed by the use of the [JENKINS:Git Client Plugin], which is only tested on official git client. Use exotic installations at your own risk. 2.5.3 2.5.2 GitHub Organization Folder Plugin Pipeline-as-Code support for a whole GitHub organization. Scans all the branches & repositories in GitHub organization and build them via Jenkins pipelines automatically 1.4 1.3 Pipeline: Basic Steps Commonly used steps for Pipelines. 2.1 2.0 Pipeline: Groovy Pipeline execution engine based on continuation passing style transformation of Groovy scripts. 2.10 2.9 Pipeline: Job Defines a new job type for pipelines and provides their generic user interface. 2.4 2.3 Pipeline: Nodes and Processes Pipeline steps locking agents and workspaces, and running external processes that may survive a Jenkins restart or slave reconnection. 2.4 2.3 Pipeline: REST API Plugin Provides a REST API to access pipeline and pipeline run data 1.7 1.6 Pipeline: Stage View Plugin Provides a swimlane view of the different stages in a pipeline. 1.7 1.6 Pipeline: Step API API for asynchronous build step primitive. 2.3 2.2 Structs Plugin Library plugin for DSL plugins that need concise names for Jenkins extensions 1.3 1.2

            oleg_nenashev Oleg Nenashev
            nitek Claus Näveke
            Votes:
            13 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: