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.
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
Step by step: Manager update in the interface
Step by step: signed offline package (three nodes)
Fields and options
| Field / action | Meaning and use |
|---|---|
| Manager-Version | Running 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. |
| Koordinator | The node the Manager runs on. The package is uploaded there and distributed from there. |
| HA-Cluster | The steps of the signed offline package require exactly three nodes. |
| Vorladen | Imports the content of the package on a node without changing running services. |
| Zeit synchron | Shows whether the clock of the node is synchronised by NTP. Without synchronisation the update cannot be applied. |
| Vertrauensanker | Shows whether the public key for signature verification is installed on the node. |
| Anhalten / Erneut versuchen | Pauses or repeats distribution and preloading. |
| Cluster prüfen (--ha-verify) | Checks the cluster again after the update has been applied. |
| Log | Output 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.