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

Digest mismatch in update center for LTS 1.480.3

XMLWordPrintable

      I encountered an issue that seems that should be fixed since i saw it appear in JIRA a couple of times before.

      When installing a fresh Jenkins LTS 1.480.3 release on Windows Server 2008 R2 x64 I can't find any plugins in "Available" and "Updates" tabs.

      I receive the following error:
      Apr 19, 2013 1:34:59 AM hudson.model.UpdateSite doPostBack
      SEVERE: <div class=error><img src='/static/9545af49/images/none.gif' height=16 width=1>Digest mismatch: 1Woxyt3oLgioZax7SGlbwYITc98= vs +JLZbigPye2eA9Fsv6sa3DW3q2s= in update center 'default'</div>

      I have tried the latest Jenkins version and I don't receive this issue. The thing is - i want to go with the LTS version since i'm installing it on a PROD environment.

          [JENKINS-17677] Digest mismatch in update center for LTS 1.480.3

          Potroshitel Jack created issue -
          Potroshitel Jack made changes -
          Fix Version/s Original: current [ 10162 ]
          sogabe made changes -
          Link New: This issue is duplicated by JENKINS-17711 [ JENKINS-17711 ]
          Potroshitel Jack made changes -
          Component/s New: plugin [ 15491 ]
          Labels Original: plugin New: plugin update updateCenter

          Potroshitel Jack added a comment -

          Hello guys, i don't wont to be ungrateful, but is this issue at least been noticed by someone?
          Because a simple message - like "will be investigated in some time" at least would be helpful.
          Maybe I haven't created the issue in the correct manner - please advice?

          Potroshitel Jack added a comment - Hello guys, i don't wont to be ungrateful, but is this issue at least been noticed by someone? Because a simple message - like "will be investigated in some time" at least would be helpful. Maybe I haven't created the issue in the correct manner - please advice?

          Mark Waite added a comment -

          I can see the same error on Jenkins 1.480.3 on a Windows 7 machine. The SEVERE message is on the console window where I started Jenkins, but is not visible anywhere in the Jenkins user interface.

          Oddly enough, my Jenkins 1.480.3 on Debian Linux does not report the digest mismatch and has not reported that digest mismatch in any of its log files from months before.

          Mark Waite added a comment - I can see the same error on Jenkins 1.480.3 on a Windows 7 machine. The SEVERE message is on the console window where I started Jenkins, but is not visible anywhere in the Jenkins user interface. Oddly enough, my Jenkins 1.480.3 on Debian Linux does not report the digest mismatch and has not reported that digest mismatch in any of its log files from months before.

          Mark Waite added a comment - - edited

          Generally, opening a new bug report for the same issue will not improve responsiveness. The new JENKINS-17711 won't help people investigate it any sooner and makes work for someone to resolve it as a duplicate.

          Mark Waite added a comment - - edited Generally, opening a new bug report for the same issue will not improve responsiveness. The new JENKINS-17711 won't help people investigate it any sooner and makes work for someone to resolve it as a duplicate.

          Preston Jennings added a comment -

          I have this issue as well with the debian 1.480.3 LTS package on ubuntu. In my opinion this is an absolute must-fix for a build branded "LTS"! Are there any workarounds?

          Preston Jennings added a comment - I have this issue as well with the debian 1.480.3 LTS package on ubuntu. In my opinion this is an absolute must-fix for a build branded "LTS"! Are there any workarounds?

          Mark Waite added a comment -

          I doubt the problem is with the LTS package itself. I assume something is incorrect on the plugins site, or on one of the plugins sites (if they are mirrored somehow).

          Mark Waite added a comment - I doubt the problem is with the LTS package itself. I assume something is incorrect on the plugins site, or on one of the plugins sites (if they are mirrored somehow).

          Kohsuke Kawaguchi added a comment -

          The digest is computed from the submitted JSON payload, and except the unlikely situation where this is broken for everyone, there must be something going on that we don't fully understand. (But how could anyone in the middle would tamper with JSON!?)

          I think we need to improve the diagnostic code so that when we issue this error, we set aside the failed JSON payload and instruct the admin to attach that in the bug report.

          Kohsuke Kawaguchi added a comment - The digest is computed from the submitted JSON payload, and except the unlikely situation where this is broken for everyone, there must be something going on that we don't fully understand. (But how could anyone in the middle would tamper with JSON!?) I think we need to improve the diagnostic code so that when we issue this error, we set aside the failed JSON payload and instruct the admin to attach that in the bug report.

            jglick Jesse Glick
            bzlom Potroshitel Jack
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: