Maintenance mode doesn't get disabled after failed upgrade

[bonjurkes]

WP enables maintenance mode when admin starts an update process (updating themes, plugins etc.) But when an update fails maintenance mode doesn't get disabled and it blocks access to wp admin.

So 2 possible options :

1-) Maintenance mode can get disabled (.maintenance file will be deleted automatically) if some upgrade or installation fails

or

2-) Maintenance mode shouldn't block access to wp-admin section, as each time admin has to delete .maintenance file from ftp when he/she wants to access wp-admin to retry updating process.

WP Version : 3.0 RC2

(In [15139]) Make upgrading global so maintenance_nag() can see it. see #13721

That fixes the nag for when the .maintenance file is not cleaned up before its ten minute expiration.

The .maintenance file expires after 10 minutes. Fixing the nag for that is probably as good as we're getting for 3.0. The .maintenance file "should" be deleted for all failure cases. Could you provide output for a failed upgrade so we can narrow down where cleanup may be missing?

Actually, i didn't wait for 10 mins .maintenance file get deleted if there is a failed update. Because if an update fails while i am performing it, i don't wait 10 minutes to login back to wp-admin. I just click back button to write ftp info or to try updating again, so i have to delete .maintenance file manually each time.

But when i click back button it shows "maintenance information".

'Could you provide output for a failed upgrade so we can narrow down where cleanup may be missing?'

Please re-open with additional steps to reproduce.

There have been quite a few support threads lately reporting sites stuck in maintenance mode after failed auto-updates. The message "an automatic WordPress update" failed. Please try again." remains even after a successful subsequent manual update...