"Auto" upgrade to 1.5.7 wasn't auto - took my application offline for ~1 month

[p. bateman]

Hi,

On 5/15/18 my app apparently auto-upgraded to version 1.5.7 from 1.5.1, however, the upgrade never fully completed until this morning when I clicked into my backend portal and clicked "OK" to complete the upgrade process. Thus my app was rendered offline for almost a full month.

In the future can you please make the auto-upgrade truly automatic and not requiring user intervention? If user action is required to complete an upgrade I think it'd be better to 1) notify the admin user that action is required, or 2) don't automate the upgrade so long as any sort of manual admin action is required.

 

[p. bateman]

This is the notification of update that I received but it didn't make any mention of a required action to finalize the update.

 

[twisted1919]

@p. bateman - It should work automatically full way and complete the upgrade process by it's own.
However, there are cases when for various reason the upgrade cannot complete and it stops at that particular step.
We're investigating this particular issue and will have a fix for it till next release.

 

[p. bateman]

Thank you! Regrettably, I don't have a screenshot of the confirmation screen in the backend where I had to click OK to proceed.

 

[twisted1919]

@p. bateman - It's fine, i managed to figure the issue and have fixed it while writing the previous reply

 

[p. bateman]

Hi @twisted1919 I experienced the exact same issue again during the auto upgrade to 1.6.1, this time with screenshots:

1. I received this auto-update notification:


2. Remembering what happened last time, I attempted to access my customer and observed that the app was offline:


3. I logged into the backend and saw this:


4. I clicked "Start upgrade process" and received this page almost instantly at which point everything was back online:



Fortunately during this upgrade cycle Mailwizz was only offline for 4 hours because I saw the upgrade email quickly knew what to do but still this is quite disruptive. I have auto-upgrade enabled in my backend. Why doesn't the upgrade fully complete automatically and instead hangs in an offline state until I click a button?

Thanks for looking into this!

 

[twisted1919]

@p. bateman - 1.6.1 fixes this issue for good, next auto-update will run perfectly fine.