Updates & versions

System Updates page

Open License & Updates → System updates. The page shows:

• the installed version and release notes;
• the latest update check;
• a compatible published version and its release notes, when available;
• package compatibility information;
• a copyable update command; and
• current or recent update progress.

Users with updates:read or updates:manage can view status. updates:manage is required to check for updates and view the host command.

Check for an update

1. Confirm Installed release matches the expected version.
2. Select Check now.
3. If current, record the check time and take no further action.
4. If an update is available, review the version, compatibility, package size, and release notes.
5. Schedule an approved maintenance window and confirm the client database and installation backups are current.

Checking does not install anything.

Apply an installer-managed update

For an installer-managed localhost or production deployment, the Update instructions card contains the authoritative Docker command for that installation and target version:

1. Select Copy update command.
2. Open a terminal on the server that runs OneView.
3. Paste the command without editing it.
4. Confirm the source version, target version, and release notes shown in the terminal.
5. Enter y only after final approval.
6. Keep the terminal attached until it reports a completed, restored, or failed outcome.

The browser does not install the update. The host command validates the release, protects the current deployment, performs the update, and checks service health. Starting another update while one is active is unsupported.

Source-managed localhost

A non-production backend started from a verified source checkout is not an installer-managed deployment. When OneView detects an eligible compatible release and safely recognizes the checkout's version declaration, Update instructions may instead show a platform- and path-specific command identified as setting the reported source version.

This command changes only the version that the local source-run backend reports for testing. It does not download, checkout, or install published source code, packages, Docker images, database changes, or other release contents. Do not treat it as proof that the checkout contains the published release.

To use the displayed source-checkout command:

1. Confirm the local checkout already contains the code you intend to test.
2. Stop the source-run backend.
3. Copy the exact command displayed by that local System Updates page and run it from the indicated environment.
4. Restart the backend using the source checkout's normal approved development command.
5. Return to System updates and confirm the locally reported version.

The displayed command accounts for the local platform and checkout path. Do not replace it with a Docker update command, copy a command from another checkout, or construct one from documentation. If OneView cannot safely identify the local version declaration, or no eligible release exists, it does not offer a source-checkout command.

Neither update path requires a manual handoff code. Do not obtain, enter, or append one to an update command.

Observe progress

For an installer-managed update, the page and terminal show customer-facing stages such as preparation, package verification, maintenance, backup, service update, health check, completion, or restoration. The browser may disconnect briefly while services restart.

• Completed — the target release is active and healthy.
• Previous release restored — the update could not complete and the previous release returned to service.
• Failed — the update or restoration needs administrator attention.

Do not edit application data, deployment configuration, or update state to change the displayed result.

A source-checkout version command does not enter these installer-managed update stages. Its expected outcome is that the restarted local backend reports the selected test version; validate the checkout and application separately.

Validate after completion

1. Confirm the installed version and healthy status.
2. Sign in through the approved HTTPS address.
3. Review license state, active sessions, vendor connections, and activity logs.
4. Run network health checks.
5. Run an approved synthetic verification for each critical enabled Sub-module.
6. Re-enable integration traffic and monitor the client-owned infrastructure.

If the update is interrupted or fails, keep normal traffic paused and follow the Update runbook. Never bypass release verification.