I'm likewise seeing this:

When trying to upgrade I see the following in the log:

I follow the url: http://updates.jenkins-ci.org/download/war/1.621/jenkins.war

Which is not found! It looks like only 1.619 is there:

What to do?

Longtrail

youch, that sounds even worse (and probably the same problem). I had only noticed the changelog wasn't up even though the new version claimed to be available. I hadn't even tried to upgrade yet.

I tried to update but it failed, I'm still running with 1.619.

The 1.621 release was aborted half way through, so exists in the Maven repo (which is the basis for the update center), but the bits do not exist on the mirrors. KK has been informed. Just wait a bit (there are no really significant changes in that release anyway).

Should a separate defect be filed for showing an update is available when one is not, or should we face similar confusion next time release is aborted?

Hi there,
Having a similar problem with sudo apt-get update
Thought I'd mention it here instead of opening another issue as it seems related.

Same issue, botched release. We have none of the native packages, and the war isn't available from the mirrors. Unfortunately KK (who does the releases and signs them with his own keys, therefore not easily shared) is at OSCON today.

OSCON is from 20-24 July, so we will have to probably wait until 27th

This missing war file is a problem if you want to install/upgrade plugins for jenkins which needs newer version of jenkins then is installed.
We cannot upgrade jenkins automatically (we get 404 when http://updates.jenkins-ci.org/download/war/1.621/jenkins.war), we will have to upgrade it manually.
It would be nice if someone just removed version 1.621 because jenkins detects it. But I guess it's not that trivial.

This issue should not be actual anymore, because there are many newer weekly releases