> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Update EVE-OS on Nodes > Use the Release Manager to stage, activate, and monitor EVE-OS version updates on individual nodes, projects, clusters, or the entire fleet. ## Introduction The Release Manager is the central place for managing EVE-OS (Edge Virtualization Engine) updates across your fleet. Use it to stage and activate EVE-OS version updates on individual nodes, groups of nodes by project, entire clusters, or your entire fleet. Updates follow a two-step workflow: 1. **Download**: EVE-OS stages the selected version on the node without rebooting it. 2. **Install**: EVE-OS activates the staged version and reboots the node. You can run these steps separately or use **Download & Install** to perform both in a single operation. ## Before You Start * You have the SysManager or SysAdmin role in your enterprise. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md). * The nodes you want to update are online and reachable. * You have reviewed the maintenance impact: running workloads are briefly interrupted when a node reboots during the Install step. ## Open the Release Manager In the sidebar, navigate to **Infrastructure > Operations > Release Manager**. The Release Manager opens to the **Nodes** tab, which lists all nodes in your fleet grouped by project. The **History** tab shows the EVE-OS image history for a selected node. ## Review Fleet EVE-OS Status The **Nodes** tab shows the current EVE-OS state of every node in your fleet. Each row shows the node name, CPU architecture, current EVE-OS version, the version downloaded and staged (if any), and the current update status. The status summary bar at the top of the table displays clickable chips for each status category: **Total**, **Needs update**, **Downloading**, **Downloaded**, **Installing**, **Up to date**, and **Failed**. Click a chip to filter the table to nodes in that state. Node statuses are: * **Needs update**: A newer EVE-OS version is available. The node has not yet downloaded it. * **Downloading**: The node is actively downloading the EVE-OS image. * **Downloaded**: An EVE-OS version is staged on the node and ready to install. * **Installing**: The node is activating the staged version and rebooting. * **Up to date**: The node is running the latest available EVE-OS version. * **Failed**: The last update attempt failed. A red triangle icon appears in the Status column. Click the icon to open the associated job record for details. While an update is in progress, the Status column shows granular sub-phase labels: **Downloading**, **Verifying**, **Initializing**, **Rebooting**, **Testing**, and others as the node moves through each stage. The Release Manager refreshes status automatically every 8 seconds while nodes are actively downloading or installing, and every 30 seconds otherwise. ## Download EVE-OS to Nodes The Download action stages an EVE-OS version on the selected nodes without rebooting them. Use this step when you want to pre-stage an update and activate it separately, for example during a maintenance window. You can trigger Download for an individual node, all nodes in a project, or a selection of nodes across projects. ### Download for an individual node 1. In the **Nodes** tab, locate the node. 2. Open the row overflow menu (the three-dot icon at the end of the row). 3. Select **Download**. 4. In the **Download EVE-OS** dialog, select the target EVE-OS version from the dropdown. The newest version compatible with the node's architecture and EVE-OS flavor is selected by default. Use the **All**, **LTS**, and **Non LTS** toggle at the top of the dropdown to filter the list. The list includes EVE-OS images your enterprise uploaded to the Library as well as the published catalog of images in Edge Infrastructure Services. The **(latest)** label marks the version marked as latest in the Library for the node's architecture. For details, see [Choose a Target EVE-OS Version](https://zededa.mintlify.site/new-ui/infrastructure-services/release-manager/update-eve-os-with-release-manager.md#choose-a-target-eve-os-version). 5. Click **Download Now**. The node begins staging the selected version. Its status changes to **Downloading** and progresses through sub-phases until it reaches **Downloaded**. ### Download for all nodes in a project 1. In the **Nodes** tab, locate the project heading row. 2. Open the project row overflow menu. 3. Select **Download**. 4. Select the target version and click **Download Now**. ### Download for a selection of nodes 1. Select the checkboxes next to the nodes you want to update. You can select nodes across multiple projects. 2. In the bulk action toolbar that appears, click **Download**. 3. Select the target version and click **Download Now**. ## Install EVE-OS on Nodes The Install action activates the EVE-OS version already staged on the selected nodes and reboots them. Run this step after Download completes. If you select Install on a node that has no version staged, the dialog displays a **Nothing to Install** message and offers to run Download or Download & Install instead. You can trigger Install for an individual node, all nodes in a project, or a selection of nodes. ### Install for an individual node 1. In the **Nodes** tab, locate the node. Its status should be **Downloaded**. 2. Open the row overflow menu. 3. Select **Install**. 4. Review the dialog, which shows the staged version that will be activated. 5. Note the warning: running workloads will be briefly interrupted during the reboot. 6. Click **Install Now**. The node reboots and activates the staged version. Its status changes to **Installing** and progresses through reboot and testing sub-phases. ### Install for all nodes in a project or a selection of nodes Follow the same steps as for Download, but select **Install** from the project overflow menu or the bulk action toolbar. ## Download and Install in One Step The **Download & Install** action downloads the selected EVE-OS version and immediately activates it, rebooting the node. Use this option when you want to complete the update in a single operation rather than staging first. Running workloads are briefly interrupted when the node reboots. 1. Open the overflow menu for the node, project, or use the bulk action toolbar. 2. Select **Download & Install**. 3. Select the target version from the dropdown. 4. Click **Download & Install Now**. ## Upgrade EVE-OS on Clusters Cluster-level EVE-OS upgrades are not currently available in the Release Manager or on the cluster detail page. Cluster upgrades apply to all member nodes as a single operation, with no separate Download or Install step. Use ZCLI to upgrade a cluster: ```bash theme={"dark"} zcli edge-node-cluster upgrade --image= ``` To check the progress of the upgrade on each member node, run: ```bash theme={"dark"} zcli edge-node-cluster show --upgrade ``` ## Monitor Update Progress During an update, the Status column in the Nodes tab reflects the current sub-phase of the operation: * **Downloading**: The node is downloading the EVE-OS image. * **Verifying**: The downloaded image is being verified. * **Initializing**: EVE-OS is preparing to activate the new version. * **Rebooting**: The node is rebooting into the new version. * **Testing**: EVE-OS is testing the new version before committing it. If the update fails, a red triangle icon appears in the Status column. Click the icon to open the job record for error details. ## Verify the Update After the node returns to an active state: 1. In the **Nodes** tab, confirm the node's status shows **Up to date**. 2. Check the **EVE Version** column to confirm the node is running the expected version. 3. Navigate to **Infrastructure > Fleet > Nodes**, open the node detail page, and confirm the node is healthy and applications are running. ## Review History The **History** tab shows the EVE-OS base-image events recorded for a single node. History is recorded per node, so first select a node from the picker at the top of the tab. The table then lists each publish and activate event with the image version, the user or system that triggered it, and the timestamp. Use this tab to audit past updates or diagnose why a node is on an unexpected EVE-OS version. See [View Update History](https://zededa.mintlify.site/new-ui/infrastructure-services/release-manager/update-eve-os-with-release-manager.md#view-update-history). To review the outcome of completed update jobs, open **Infrastructure > Operations > Jobs**. ## Next Steps > [card] [Node Status and Health](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/node-status-and-health.md) > > Interpret node status after an EVE-OS update. > [card] [Node Details](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/node-details.md) > > Inspect the EVE-OS version, applications, and storage on a node after the update. > [card] [Manage Node Lifecycle](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/manage-node-lifecycle.md) > > If a manual reboot, deactivate, or recovery operation is needed after an update.