Rebooting / shutting down the eBlocker by the user should not be allowed during an update

[eblosug]

The UI allows rebooting or shutting down the eBlocker if:

• automatic updates are currently in progress
• the API method /api/adminconsole/updates/status has not been called yet.

In this case a reboot or shutdown would interrupt the update.

The above API method is only called if the admin loads one of the following tabs:

• License & Update / Update
• Blocker

[eblosug]

The issue does not occur, because the updater uses the UpdateStatusObserver class to set the system state to UPDATING temporarily.

[eblosug]

The issue still occurs. Although the system status at /api/adminconsole/systemstatus has the correct executionState UPDATING, the updatingStatus element does not exist. Therefore the updating screen in the UI does not show any progress.

AND: the settings can be opened again in the browser by entering eBlocker's IP in the URL bar. The updating screen does not appear and it is possible to shutdown the eBlocker.

[eblosug]

It's even worse:

• Go to License & Update / Update and start a manual update
• The updating screen showing progress is shown
• Close the browser window
• Open a new window and enter eBlocker's IP to load the settings
• The updating screen is not shown although the eBlocker is still updating
• Shut down the eBlocker, interrupting the update.

[eblosug]

At least the backend should make sure that the user can not initiate a reboot or shutdown during an update.