Reevaluate the GUI upgrade language presented to the user
When a user is performing an upgrade using the Web GUI they are presented with this message after the files are copied and the reboot is about to be executed:
Upgrade is complete. Rebooting in 10 seconds.
The Web GUI then tells them:
Page will automatically reload in N seconds.
That is misleading. The upgrade is not complete. There is much work still to be done after the system reboots. Slower systems with lots of packages might take several minutes before the upgrade is actually completed but the Web GUI user is not presented with any information indicating that is the case.
Anecdotally, this results in users experiencing (probably reasonable, based on the information they are given, since it looks like they only need to wait for the device to reboot) impatience and they pull the power while packages are being installed after the reboot. This will almost certainly result in a "bricked" device and the upgrade process is blamed as the cause.
I believe this can be better by:
- Presenting language that more accurately reflects reality in the Web GUI.
- Perhaps suggesting they watch the console to determine when the upgrade is actually completed.
- Provide a way for the inside interface to pick up the upgrade process log via the web browser before it is actually completed. This is probably a pretty big ask.
Updated by Jordan Greene about 1 year ago
The message "System is going to be upgraded. Rebooting in 10 seconds" appears in the verbose console output portion of the GUI but above that on the update page, more prominently displayed is still "System update successfully completed." see attached