Critical On an Ubuntu 12.04.4 LTS box, we updated a config which then propegated changes from a bunch of plugins via Jenkins->Manage Jenkins->Configure System and when added some info for an Artifactory server. This caused unknown behavior that was causing all attempts to edit Job configs to cyclically request credentials, never-ending.
To recover, we removed newly propegated XML files from /var/lib/jenkins and made backups of what was left, then viewed the old `good` configs with the jobHistory plugin, saved those as XML files, and then copied them into /var/lib/jenkins
This reversed the issue of no longer being able to edit configs, but injected a new issue. We cannot successfully install any new plugins with the Web-GUI, nor can we `Check Now`
Proxy info not set in Web-GUI but on the ubuntu box itself. No proxy info should have been updated as we were just addressing plugins.
Attachment shows example error for "java.io.IOException: Downloaded file /var/lib/jenkins/plugins/plugin_name.jpi.tmp does not match expected SHA-1, expected 'SomeSHA=', actual 'SomeOtherSha='"
When trying Check Now with http://updates.jenkins-ci.org/update-center.json, getting this error also completely shown in other attachment: "javax.servlet.ServletException: java.lang.IllegalArgumentException: Could not find (numeric) updateCenterVersion in..."
We then tried updating Jenkins from 2.x to 2.7 – this did not change the behavior, which surprised us to be frank.
How can we fix the update center queries, even if it is a workaround? Right now all plugins have to be handled manually...
- is related to
-
JENKINS-32796 Can't update plugins: incorrect checksum
-
- Resolved
-
[JENKINS-38050] Unable to successfully compare SHA-1 for all plugins using Web-GUI for Plugins Update Center
Dan Di
created issue -
Dan Di
made changes -
| Description |
Original:
On an Ubuntu 12.04.4 LTS box, we updated a config which then propegated changes from a bunch of plugins. This caused unknown behavior that was causing all attempts to edit Job configs to cyclically request credentials, never-ending. To recover, we removed newly propegated XML files from /var/lib/jenkins and made backups of what was left, then viewed the old `good` configs with the jobHistory plugin, saved those as XML files, and then copied them into /var/lib/jenkins This reversed the issue of no longer being able to edit configs, but injected a new issue. We cannot successfully install any new plugins with the Web-GUI, nor can we `Check Now` Proxy info not set in Web-GUI but on the ubuntu box itself. No proxy info _should_ have been updated as we were just addressing plugins. Attachment shows example error for "java.io.IOException: Downloaded file /var/lib/jenkins/plugins/plugin_name.jpi.tmp does not match expected SHA-1, expected 'SomeSHA=', actual 'SomeOtherSha='" When trying Check Now with http://updates.jenkins-ci.org/update-center.json, getting this error also completely shown in other attachment: "javax.servlet.ServletException: java.lang.IllegalArgumentException: Could not find (numeric) updateCenterVersion in..." We then tried updating Jenkins from 2.x to 2.7 -- this did _not_ change the behavior, which surprised us to be frank. How can we fix the update center queries, even if it is a workaround? Right now all plugins have to be handled manually... |
New:
On an Ubuntu 12.04.4 LTS box, we updated a config which then propegated changes from a bunch of plugins via Jenkins->Manage Jenkins->Configure System and when added some info for an Artifactory server. This caused unknown behavior that was causing all attempts to edit Job configs to cyclically request credentials, never-ending. To recover, we removed newly propegated XML files from /var/lib/jenkins and made backups of what was left, then viewed the old `good` configs with the jobHistory plugin, saved those as XML files, and then copied them into /var/lib/jenkins This reversed the issue of no longer being able to edit configs, but injected a new issue. We cannot successfully install any new plugins with the Web-GUI, nor can we `Check Now` Proxy info not set in Web-GUI but on the ubuntu box itself. No proxy info _should_ have been updated as we were just addressing plugins. Attachment shows example error for "java.io.IOException: Downloaded file /var/lib/jenkins/plugins/plugin_name.jpi.tmp does not match expected SHA-1, expected 'SomeSHA=', actual 'SomeOtherSha='" When trying Check Now with http://updates.jenkins-ci.org/update-center.json, getting this error also completely shown in other attachment: "javax.servlet.ServletException: java.lang.IllegalArgumentException: Could not find (numeric) updateCenterVersion in..." We then tried updating Jenkins from 2.x to 2.7 -- this did _not_ change the behavior, which surprised us to be frank. How can we fix the update center queries, even if it is a workaround? Right now all plugins have to be handled manually... |
Dan Di
made changes -
| Summary | Original: Unable to successfully compare SHA-1 for all plugins using Web-GUI | New: Unable to successfully compare SHA-1 for all plugins using Web-GUI for Plugins Update Center |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Link |
New:
This issue is related to |