EasyUC
4.9.49

Installation, updates & backup

Updating the EasyUC Manager

Bring the Manager up to date via the Manager-Update page, with the offline package at the console or with the signed offline package for three nodes.

EasyUC · Version 4.9.49

In EasyUC: Manager → Manager-Update; Manager → System-Updates

What it is for

The EasyUC Manager is a product of its own with its own version number. It consists of the Manager interface, the Manager API with the built-in operator and the definition of the EasyUC resource. An EasyUC update does not change the Manager; it is updated separately.

EasyUC 4.9.49 needs Manager 2.0.4 or later; new appliances already come with Manager 2.0.11 from the OVA. On older appliances, update the Manager first and then EasyUC.

There are three routes: the Manager-Update page in the Manager interface with the signed file easyuc-manager-update-<version>.eucupg, the offline package for the Manager at the console of the first node, and the signed offline package on the System-Updates page for clusters with exactly three nodes.

Prerequisites

  • The Manager update file from the customer portal: Downloads → Other components → Tools, currently easyuc-manager-update-2.0.11.eucupg. Which route applies to your package is stated in the release documentation.
  • For the offline package: console access with administrator rights on the first node.
  • For the Manager-Update page: sign-in to the Manager and enough free space on the installation server. Running updates and backups must be finished.
  • For the signed offline package: exactly three nodes in state Ready, synchronised time on all nodes and VM snapshots of all nodes.
  • In clusters with several nodes, the Manager image must be present on all nodes so that the Manager can start on another node if a node fails.

Step by step: offline package on the console

  1. Copy the Manager package to the first node.
  2. Unpack it and start the included script apply-manager-update.sh with administrator rights, as described in the accompanying documents.
  3. The script imports the images, distributes the Manager image to the other nodes, updates the definition of the EasyUC resource and runs the Manager update.
  4. Wait for the final check of the script. If the update fails, the script reverts the change itself.
  5. Log in to the Manager again. The version is shown in the navigation below the logo ("Version …").

Step by step: Manager update in the interface

  1. In the Manager, choose Manager-Update at the top right or the Manager-Update entry in the System menu.
  2. Drag the .eucupg file onto the area Manager-Update hier ablegen or click to select it. The signature is contained in the file; a paused upload resumes with the same file.
  3. Wait until the Manager has checked package content, signature and requirements. Produktionssignatur then shows "Gültig und geprüft", next to Installierte Manager-Version and Neue Manager-Version.
  4. Choose Jetzt installieren (install now) and confirm the prompt.
  5. The Manager restarts and is briefly unavailable; the update continues even if the browser is closed. Wait for the message that the new version was installed successfully.

Step by step: signed offline package (three nodes)

  1. Open the System-Updates page in the Manager. The card EasyUC-Update (signiertes Offline-Paket) is at the top.
  2. Drag the .run file and the matching .run.sig together into the drop area.
  3. Select Hochladen und prüfen and confirm with the Manager password. The upload can be resumed.
  4. Wait for "Signatur gültig". If "Signatur ungültig – Paket nicht verwenden" appears, stop.
  5. Select Auf allen Knoten vorladen. The nodes are prepared one after the other; running services do not change.
  6. In the node table, check the columns Ready, Datei, Vorladen, Vorbereitet, Zeit synchron, Frei and Vertrauensanker.
  7. In the Einspielen section, select Prüfen (--ha-check).
  8. Create VM snapshots of all nodes and tick VM-Snapshots aller Knoten erstellt in Gefahrenbereich: Update einspielen.
  9. Type the confirmation word shown and select Update einspielen.
  10. Leave the page open. The Manager restarts during the run; the page keeps polling the state and then shows result and log.
  11. Finally select Hochgeladene Dateien löschen.

Fields and options

Fields and options
Field / actionMeaning and use
Manager-VersionRunning version of the Manager. The addition "von der Vorabprüfung nicht unterstützt" means that the package does not know this level as a starting version.
KoordinatorThe node the Manager runs on. The package is uploaded there and distributed from there.
HA-ClusterThe steps of the signed offline package require exactly three nodes.
VorladenImports the content of the package on a node without changing running services.
Zeit synchronShows whether the clock of the node is synchronised by NTP. Without synchronisation the update cannot be applied.
VertrauensankerShows whether the public key for signature verification is installed on the node.
Anhalten / Erneut versuchenPauses or repeats distribution and preloading.
Cluster prüfen (--ha-verify)Checks the cluster again after the update has been applied.
LogOutput of the selected step, refreshed every three seconds during a run.

Check the result and troubleshoot

  • The navigation of the Manager shows the new version below the logo, and all Manager pages are reachable.
  • The EasyUC-Update page is present and shows the running EasyUC version under Installiert.
  • "Bitte eine neuere Manager-Version hochladen." (upload a newer version): the file is not newer than the running Manager. "Das Paket hat keine gültige Produktionssignatur oder wurde verändert." (invalid signature): download the file again from the customer portal.
  • "Noch nicht möglich, es fehlt: …" when applying: the list names the open prerequisites, for example nodes that are not prepared or missing time synchronisation.
  • "Auf den Knoten läuft gerade schwere I/O … Hochladen erst danach": wait until the running import has finished.
  • "Manager nicht erreichbar. Neuer Versuch in wenigen Sekunden …" is expected while the update is being applied. The run continues on the nodes.
  • "Auf dem Installationsserver ist nicht genügend freier Speicherplatz." (not enough free space): free up space, for example discard an old package with Paket entfernen, and try again.
  • After the Manager has been replaced, you may have to log in again because older logins become invalid.

Related chapters