Details

    • Type: Bug
    • Status: Reopened
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Environment:
      Ubuntu 10.4 with apt-get install

      Description

      Errorlog Jenkins when i click update.

      24.09.2011 23:26:10 hudson.model.UpdateSite doPostBack
      SCHWERWIEGEND: <div class=error><img src='/static/89477826/images/none.gif' height=16 width=1>Digest mismatch: 3zSmH0+egpPemOEVkgRcfBl9eMk= vs 7mr8qItL8f9SuaOaVfCRlQGYFZU= in update center 'default'</div>

      This Commit change the signature Check.
      https://github.com/jenkinsci/jenkins/commit/3a38a67cf8838a04fe2e3c7b938ab9d305c99367

      After this patch, no update file json is fetched.

        Activity

        Show
        kohsuke Kohsuke Kawaguchi added a comment - This is fixed in https://github.com/jenkinsci/backend-update-center2/commit/d667ea0953ce49e1459e4b92b72c9eb9627e4229 and https://github.com/jenkinsci/jenkins/commit/1eb0c64abb3794edce29cbb1de50c93fa03a8229
        Hide
        scm_issue_link SCM/JIRA link daemon added a comment -

        Code changed in jenkins
        User: Kohsuke Kawaguchi
        Path:
        src/main/java/org/jvnet/hudson/update_center/Main.java
        http://jenkins-ci.org/commit/backend-update-center2/a9bdef29f24f78f452c0dd3cbdc414dd55346fcc
        Log:
        JENKINS-11110 revisiting the fix.

        Our "fixing" the update center to serve the correct bits break existing Jenkins out there because they see the signature mistamatch and refuse to accept those UC data. This in turn prevents them to auto-upgrade, cutting off their path to receive fix and strand them into the current release.

        So instead, I'm keeping the legacy generation code as-is and then generating the correct digest and signature into separate names. Newer Jenkins shall then check the new values first.

        Show
        scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jvnet/hudson/update_center/Main.java http://jenkins-ci.org/commit/backend-update-center2/a9bdef29f24f78f452c0dd3cbdc414dd55346fcc Log: JENKINS-11110 revisiting the fix. Our "fixing" the update center to serve the correct bits break existing Jenkins out there because they see the signature mistamatch and refuse to accept those UC data. This in turn prevents them to auto-upgrade, cutting off their path to receive fix and strand them into the current release. So instead, I'm keeping the legacy generation code as-is and then generating the correct digest and signature into separate names. Newer Jenkins shall then check the new values first.
        Hide
        scm_issue_link SCM/JIRA link daemon added a comment -

        Code changed in jenkins
        User: Kohsuke Kawaguchi
        Path:
        core/src/main/java/hudson/model/UpdateSite.java
        http://jenkins-ci.org/commit/jenkins/6dd6817933272d24da20377ec29bed4e394334aa
        Log:
        [FIXED JENKINS-11110] use different attribute names to avoid catch-22 situation with old Jenkins.

        In this way we can keep both new and old happy.

        Show
        scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/6dd6817933272d24da20377ec29bed4e394334aa Log: [FIXED JENKINS-11110] use different attribute names to avoid catch-22 situation with old Jenkins. In this way we can keep both new and old happy.
        Hide
        scm_issue_link SCM/JIRA link daemon added a comment -

        Code changed in jenkins
        User: Kohsuke Kawaguchi
        Path:
        core/src/main/java/hudson/model/UpdateSite.java
        http://jenkins-ci.org/commit/jenkins/6dd6817933272d24da20377ec29bed4e394334aa
        Log:
        [FIXED JENKINS-11110] use different attribute names to avoid catch-22 situation with old Jenkins.

        In this way we can keep both new and old happy.

        Show
        scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/6dd6817933272d24da20377ec29bed4e394334aa Log: [FIXED JENKINS-11110] use different attribute names to avoid catch-22 situation with old Jenkins. In this way we can keep both new and old happy.
        Hide
        dogfood dogfood added a comment -
        Show
        dogfood dogfood added a comment - Integrated in jenkins_main_trunk #1179
        Hide
        halkeye Gavin Mogan added a comment -

        sorry, didn't notice it would be fixed again next release.

        Show
        halkeye Gavin Mogan added a comment - sorry, didn't notice it would be fixed again next release.
        Hide
        mdp mdp added a comment -

        Should this be working now?
        My Jenkins 1.432 currently logs digest mismatches.

        Show
        mdp mdp added a comment - Should this be working now? My Jenkins 1.432 currently logs digest mismatches.
        Hide
        philipp_nanz Philipp Nanz added a comment -

        As far as I understand, this will be fixed in the upcoming 1.434.

        Show
        philipp_nanz Philipp Nanz added a comment - As far as I understand, this will be fixed in the upcoming 1.434.
        Hide
        mdp mdp added a comment -

        1.434 is released and 1.432 does not want to upgrade to it any more than to 1.433. A digest mismatch is still logged.
        Does it suggest that there will be no possibility of automatic update from 1.432?

        Show
        mdp mdp added a comment - 1.434 is released and 1.432 does not want to upgrade to it any more than to 1.433. A digest mismatch is still logged. Does it suggest that there will be no possibility of automatic update from 1.432?
        Hide
        mdp mdp added a comment -

        Upgrade after a downgrade to 1.431 worked.

        Show
        mdp mdp added a comment - Upgrade after a downgrade to 1.431 worked.
        Hide
        scm_issue_link SCM/JIRA link daemon added a comment -

        Code changed in jenkins
        User: Kohsuke Kawaguchi
        Path:
        core/src/main/java/hudson/model/UpdateSite.java
        http://jenkins-ci.org/commit/jenkins/fb3d0d4f9be38414ef1e3ecf631bafb1e081b79a
        Log:
        [FIXED JENKINS-11110] use different attribute names to avoid catch-22 situation with old Jenkins.

        In this way we can keep both new and old happy.
        (cherry picked from commit 6dd6817933272d24da20377ec29bed4e394334aa)

        Compare: https://github.com/jenkinsci/jenkins/compare/ac8e1c0...fb3d0d4

        Show
        scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/fb3d0d4f9be38414ef1e3ecf631bafb1e081b79a Log: [FIXED JENKINS-11110] use different attribute names to avoid catch-22 situation with old Jenkins. In this way we can keep both new and old happy. (cherry picked from commit 6dd6817933272d24da20377ec29bed4e394334aa) Compare: https://github.com/jenkinsci/jenkins/compare/ac8e1c0...fb3d0d4
        Hide
        cforce cforce added a comment -

        We still have that problem with jenkins 1.436

        SEVERE: <div class=error><img src='/jenkins/static/dd4c37f3/images/none.gif' height=16 width=1>Digest mismatch: g/BbLQXAEOCP7hIkNmSNFD7oQ4E= vs 8E9m3grlXzZPJHnJ6D+lbuIKQTg= in update center 'default'</div>

        At which version it has beed fixed?

        Show
        cforce cforce added a comment - We still have that problem with jenkins 1.436 SEVERE: <div class=error><img src='/jenkins/static/dd4c37f3/images/none.gif' height=16 width=1>Digest mismatch: g/BbLQXAEOCP7hIkNmSNFD7oQ4E= vs 8E9m3grlXzZPJHnJ6D+lbuIKQTg= in update center 'default'</div> At which version it has beed fixed?
        Hide
        jljogi Joachim Langenbach added a comment -

        I'm running Jenkins version 1.446 on a debian sid system. When trying to check the update center, the message

        SCHWERWIEGEND: <div class=error><img src='/jenkins/static/173b84ac/images/none.gif' height=16 width=1>Digest mismatch: 8pbYLzdwmIOuMHSD1hfK1Awu+wk= vs LExmiP3TXmyTv4cnM6OwkXSgTY4= in update center 'default'</div>

        appears at the jenkins log. Strange is, that an installation of the same jenkins version on Gentoo does not have this problems.

        Show
        jljogi Joachim Langenbach added a comment - I'm running Jenkins version 1.446 on a debian sid system. When trying to check the update center, the message SCHWERWIEGEND: <div class=error><img src='/jenkins/static/173b84ac/images/none.gif' height=16 width=1>Digest mismatch: 8pbYLzdwmIOuMHSD1hfK1Awu+wk= vs LExmiP3TXmyTv4cnM6OwkXSgTY4= in update center 'default'</div> appears at the jenkins log. Strange is, that an installation of the same jenkins version on Gentoo does not have this problems.
        Hide
        danielbeck Daniel Beck added a comment -

        Does this issue still occur on recent versions of Jenkins?

        Show
        danielbeck Daniel Beck added a comment - Does this issue still occur on recent versions of Jenkins?

          People

          • Assignee:
            Unassigned
            Reporter:
            boonkerz Thomas Peterson
          • Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated: