Browser-Based Update and Rollback

Energy Logserver can run the update from the Cockpit module, the administrative interface available in a web browser. The same module drives both directions of the operation, the update to the new release and the rollback to the previous one, so an administrator who installs a package from the browser also reverts it from there. The administrator carries out the whole operation alone, without the system console and without involving the vendor or the supplier.

Note

The Software updates view comes from the Cockpit plugin that the vendor ships with the update package. Where the plugin is not present, upgrade from the console as described in Version-Specific Upgrades.

Before you start

The vendor delivers the update as a single package file with the .elsupdate extension. Copy it to the workstation from which you open Cockpit, then log in to Cockpit on the node you are updating and go to Tools > Software updates.

Updating the system

  1. In Upload update package, select the .elsupdate file delivered by the vendor.

  2. Select Validate package. The module verifies the checksum and the signature of the package, checks that the release is compatible with the installed one, and reports the version, the contents and the size of the package.

  3. Under Pre-update actions, leave Create configuration backup and Create system snapshot selected. The backup and the snapshot are what the rollback procedure restores later.

  4. Select Start update.

  5. Follow Update status on the right side of the page. The module reports each stage as it finishes: package verification, configuration backup, system snapshot, package installation, service update, and the health check that closes the process.

The update covers the Energy Logserver components and the services that work with them. System information shows the installed release and the release the package upgrades to, so both are visible before and during the operation.

Rolling back to the previous version

Rollback runs through the same stages. When the system misbehaves after an update, the administrator starts the rollback from the same module, and it restores the previous packages, the configuration from the backup and the system snapshot that matches them. For the console procedure and for what to check once the previous version is back, see Rollback Procedures.

Scope of the operation

The administrator performs no manual operations in the operating system. The whole update is started and supervised from the browser, and the underlying operating system configuration stays untouched.