Upgrading

This is the starting point for upgrading HPE Morpheus Software. Pick your Manager topology, complete the appliance package upgrade, then finish any HVM Host Agent or cluster layout steps that apply.

Tip

For HVM deployments, see the HVM Deployment Upgrade Guide for a cohesive end-to-end upgrade sequence covering Manager, cluster, and agent upgrades in the correct order.

Important

Always back up the appliance database before upgrading. Confirm free space for new node and VM node packages (v9.1.0 needs about 3.5 GB under the package repo). After package install and before morpheus-ctl reconfigure, you may reclaim space with:

sudo rm -Rf /var/opt/morpheus/package-repos/*

Application upgrades do not replace Ubuntu base-OS maintenance on the HPE Morpheus Manager QCOW2 image. See Morpheus Manager Base OS Updates.

Upgrade procedures

Choose your path

Deployment

What to follow

Typical package

Manager VM / AIO (HPE Morpheus Manager QCOW2 or single appliance)

Single Node/AIO Appliance Upgrades — Debian/Ubuntu section first

.deb on the Manager VM

Single-node on your own guest OS

Single Node/AIO Appliance Upgrades — Debian or RPM section for that OS

.deb or .rpm

3-Node HA (rolling across app nodes)

3-Node HA Upgrade

.deb or .rpm per app node

Full HA (external MySQL, RabbitMQ, search)

Full HA Upgrade

.deb or .rpm on app nodes only

HVM clusters (after the Manager is upgraded)

HVM Clusters After Manager Upgrade

Layout/rolling update + Host Agent as needed

  1. Identify the topology from the table above and open that procedure.

  2. Upgrade every Manager / app node with the release package, then morpheus-ctl reconfigure. For HA, use the rolling or coordinated sequence in the 3-Node or Full HA guide.

  3. Confirm the UI is healthy — Refresh your browser and wait for the loading screen to finish. Only if the UI does not load or stalls, run morpheus-ctl tail morpheus-ui.

  4. If you run HVM, complete Host Agent and layout/rolling updates as described in HVM Clusters After Manager Upgrade.

  5. Optionally apply Manager base-OS updates (Morpheus Manager Base OS Updates) in a separate maintenance window from the application package upgrade.

Packages and compatibility

Release packages are available from My HPE Software Center (and historically from Morpheus Hub package URLs). Minimum upgrade versions, rolling-upgrade eligibility, and component notes are in v9.1.0 Compatibility & Breaking Changes and the current release notes. High-level package and backup requirements are summarized in Upgrading Overview.

After the Manager upgrade: Agents

Do not treat a generic UI Agent notification as a requirement to upgrade every Agent type. Update only the Agents called out by the release or by a documented workflow.

HVM Host Agents: After Manager patch and minor releases that do not include an HVM layout update, manually upgrade Host Agents so Hosts receive quorum, health-check, and telemetry improvements. Use Upgrade Agent (or Download Agent Script) on each Host detail page. Details: HVM Clusters After Manager Upgrade.

Layout-driven exception: The HVM layout 1.2 → 1.3 cluster update requires Host Agent 3.2.7 or later and upgrades an older Host Agent automatically before layout scripts run. That minimum applies to that layout transition only; it is not a general requirement for every Manager upgrade. See Upgrading Clusters.

If the UI requests an Agent update but the component and required version are not identified by a release-specific workflow, preserve the notification and contact HPE Support rather than updating unrelated Agents.