Upgrading Overview


Known issue with embedded Elasticsearch upgrade: When upgrading to v5.4.8, v5.4.9 or v5.5.1, there is a potential issue with embedded Elasticsearch clustering on rolling upgrades and existing data migration for all embedded Elasticsearch architechtures. Refer to the v6.0.8 LTS Release Notes for additional informaiton.

Morpheus Packages

Morpheus Release Package urls can be obtained from https://morpheushub.com

Upgrade Requirements


Morpheus v6.0.8 contains new node and VM node packages that require 3.5GB of storage. It is safe to run sudo rm -Rf /var/opt/morpheus/package-repos/* after v6.0.8 package installation and before reconfigure to clean old node and VM node packages from the package-repo when appliance free space is needed.


BACKUP YOUR DATABASE before the upgrade! You can use the appliance backup job in Morpheus, then rollback and restore your appliance if needed. Make sure you download the backup before you do the upgrade!

v6.0.8 Compatibility & Breaking Changes

When installing and upgrading to Morpheus v6.0.8, refer to the following to ensure compatibility.

Breaking Changes

  • 6.2.2, 6.0.7 contain embedded MySQL v8 upgrade. BACKUP YOUR DATABASE PRIOR TO UPGRADE when using embedded MySQL (all-in-one appliances).

  • 6.0.0: NSX-V support is deprecated though still supported as of Morpheus 6.0.0. It will be removed and unsupported in 6.1.1 and higher.

  • 6.0.0+: In Morpheus 6.0.0+, many third party integrations have been moved out of the core installer package and converted to Morpheus plugins. As a result, during the upgrade process your appliance will need to be able to access share.morpheusdata.com, the online repository for all Morpheus plugins. Where this is not possible, users may instead apply the supplemental installer package which is also available at Morpheus Hub alongside the main installer package.

  • 6.0.0+: In Morpheus 6.0.0+, older service specific system provided Instance Types and Layouts were deprecated and disabled. Updating to 6.0.0 will not affect existing Instances that are associated with the disabled types, however existing catalog item configurations, blueprints and api requests that use disabled Instance Types and layouts will need to be updated.

  • 5.5.2: VM Node Packages: Due to build java version requiremnets, the i386.deb and i386.rpm (32-bit) VM Node Packages can no longer be updated, and remain on v3.2.9.

  • 5.4.12: Guacd: Guacd is now complied iwth libssh2-1.10.0 on all platforms. Appliances on SLES15 may need openssl-devel manually installed for guacd to succesfully compile.

  • 5.4.12: Session Manager: Morpheus features a new session manager that was necessary in order to resolve expiring connections from the agents due to a Spring framework update. This new session manager no longer requires Sticky Sessions and they can now be turned off at the load balancer if so desired. However, keeping them on is totally reasonable as well as it reduces overall system load. Rolling restarts no longer kick you out of your session if sticky sessions are off as it distributes your session data across the morpheus nodes in an HA environment. Additionally, overall system load is reduced as a result of the new session manager.

  • 5.4.9: Morpheus 5.4.9 adds the “Provisioning: State” Role permission. This permission determines access to the State tab for Terraform-backed Instances and is set to “None” by default. On upgrade, only System Admin users will be able to see the State tab for these Instances. For other users who should have this access, edit their Roles to include “Provisioning: State” permissions.

  • 5.4.5: Warning: Database indexes added for account_usage and metadata_tag tables. Customers with very large account_usage and/or metadata_tag tables (10 million+) may experience slower initial morpheus-ui loading time after upgrading to 5.4.5, as well as additional database load.

  • 5.4.5: ‘AVI Load Balancer’ renamed to ‘NSX Advanced Load Balancer’

  • 5.4.5: Cloud Types disabled by default: Dell, HPE (NOT HPE Oneview), Supermicro and Cloud Foundry. Users would still be able to re-enable this clouds in the appliance settings. Does not affect existing Clouds.

  • 5.4.5: A10 Load Balancer type has been disabled, and will no longer be an option when adding new Load Balancers. Contact Morpheus if you need to re-enable A10 Load Balancer option. This does not affect existing Load Balancers.

  • 5.4.5: Morpheus Cluster type “Combo Cluster” renamed to “KVM/Docker Cluster”

  • 5.4.5: Greenfield managed vm’s (provisioned with Morpheus) can no longer be deleted in Morpheus without removing the actual vm/infrastructure. Restriction does not apply to brownfield vm’s that have been converted to managed.

  • 5.4.4: The Venafi and AppDynamics integrations are deprecated in v5.4.4 and will be removed in v5.4.5. AppDynamic will return as a plugin at a later date.

  • 5.4.4: The morpheus-ui logging configuration file has changed from logback.groovy to logback.xml in v5.4.4 (/opt/morpheus/conf/logback.xml). The logback.groovy file from previous versions can be removed, and any updates to logback.groovy will not result in any logging configuration changes.

  • 5.4.3: vCloud Director: Support for integrations with vCD 9 ended

  • 5.4.3: Morpheus Worker/Gateway v5.4.3 packages are now available. Existing Worker & Gateway nodes must be upgraded to v5.4.3 for compatibility with Morpheus v5.4.3 Appliances.

  • 5.4.2: vCloud Director: vCD 9.x will no longer be supported by Morpheus

  • 5.4.2: ServiceNow: Instance and Blueprint specific exposures will be removed from ServiceNow plugin support. More advanced configurations of Instances and Blueprints, in addition to Workflows, can be exposed utilizing Catalog Items

  • 5.4.2: After upgrading, it is recommended that you manually perform one “Daily” refresh Amazon Clouds to ensure availability of Amazon Service Plans for each region. To manually refresh a Cloud, navigate to Infrastructure > Clouds > (Selected Amazon Cloud) and select “Daily” from the REFRESH dropdown menu. If this is not done, Morpheus may not show Amazon Service Plans in the provisioning wizard until after Midnight UTC following the upgrade when the next automatic Daily sync would run.

  • 5.3.4: Major UI navigation structure changes. Refer to the Navigation Updates reference table

  • 5.3.3: Support for OpenStack v2 Identity API is removed

  • 5.3.2+: The local code repository path moved from /var/opt/morpheus/morpheus-ui/repo to /var/opt/morpheus/morpheus-local/repo to reduce potential shared storage issues and performance restrictions. The reconfigure process creates the folders and sets the paths in application.yml, no manual intervention is needed unless symlinks exisit on /var/opt/morpheus/morpheus-ui/repo/git which will need to be removed prior to reconfiguring - 5.3.2+ The deprecated /var/opt/morpheus/morpheus-ui/repo path will be automatically deleted in a future release but can be manually recursively deleted at any time for storage reclamation.

  • 5.3.2+: Provisioning ‣ Deployments has been moved to Provisioning ‣ Code ‣ Deployments

  • 5.2.9: OpenStack v2 Identity API is deprecated as of v5.2.9 (and is removed as of v5.3.3)

  • 5.2.6, 5.3.1: Appliance & Agent java version updated to 8u292-b10. jdk8u292 disables TLS 1.0 and 1.1 by default

  • 5.2.3+: codeready (codeready-builder-for-rhel-8-x86_64-rpms) repo access required for RHEL 8+ Appliances, replacing the previous PowerTools/powertools requirement

  • 5.2.1 & 4.2.5: API: Metadata: Metadata tags now referred to as tags and labels now referred to as labels. Previously metadata tags were referred to as metadata and labels were referred to as tags

  • 5.0.0+: When upgrading to 5.0.0+ from 4.x.x, any bearer tokens that have been generated are deleted which requires users to request new bearer tokens

  • 4.2.4: For appliances with externalized MySQL databases, due to MySQL deprecation of the “EDT” timezone you may need to update your database timezone to UTC or another compatible value. If this is not done, you will receive errors referencing timezone and Morpheus will not start. Morpheus should handle this change automatically for all-in-one appliances.

  • 4.2.1+: Tasks: Python: Virtual environment are now used for Python Tasks. Note: virtualenv is required on all Appliance App nodes

  • 4.2.1+: Puppet: Morpheus integration now supports version 6+. Puppet versions prior to 6 are no longer supported

  • 4.2.1+: Clouds: VirtualBox, VirtuSteam, and MetaCloud Cloud Types are no longer supported or available

  • 4.2.1+: Appliance: OS: Ubuntu 14.04 has reached its end of life (EOL) and is no longer supported as a Morpheus Appliance Host Operating System. Any Morpheus Appliance running on 14.04 must be upgraded to 16.04, 18.04, 20.04 or 22.04 BEFORE upgrading to 4.2.1+. Upgrades on 14.04 will not succeed

Morpheus Application OS

Morpheus can be installed on the following platforms. Please note the table below is for Morpheus Application OS support, not Morpheus Agent OS Support.


If CentOS 8.2 is pinned to 8.2.2004 vault, the PowerTools repository will need to be pinned to 8.2.2004 to access freerdp-libs 2.0.0

Supported Appliance Operating Systems




Amazon Linux



7.x. 8.x (stream) 9.x (stream)


10, 11


7.x, 8.x, 9.x

Oracle Enterprise Linux (OEL)

7.x, 8.x


12, 15


18.04, 20.04, 22.04

14.04 is no longer supported for Appliance OS. Note: 14.04 is still supported by the Morpheus Agent.


No Service Version Changes from v6.0.7

v6.0.8 Service Versions & Compatibility
v6.0.8 Service Versions & Compatibility


Compatible Branch

Morpheus Installer Version

Updated in v6.0.8

Plugin API


Morpheus Worker



v5.7, v8.0



v5.7, v8.0













1.1.1t, 1.0.2u (FIPS)



Java (macOS agent)


Morpheus Agent & Node Package Versions
v6.0.8 Agent & Node Package Versions



v6.0.8 changes from v6.0.7

Morpheus Node and VM Node Packages


Updated to 3.2.18

Morpheus Linux Agent

No change

Updated to v2.4.2

Morpheus Windows Agent


No change

Morpheus macOS Agent


No change


Security Advisories

Advisory ID



Updated On


Critical ⬛️

Morpheus through 5.4.3 (which run Java 8) are confirmed to be impacted, Morpheus through 5.5.1-1 (for customers on 5.5.x Standard installations) and 5.4.8-2 (for customers on 5.4.x LTS installations) are potentially impacted if the vulnerability is found on Java 11.



High 🟥

An XXE issue was discovered in Morpheus through 5.2.16 and 5.4.x through 5.4.4. A successful attack requires a SAML identity provider to be configured.


Upgrade Paths & Methods

The following table shows supported version upgrade paths and methods.

From Version To Version
5.5.0 → 5.5.1 5.5.2 5.5.3 6.0.0 6.0.1 6.0.2 6.0.3 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
5.5.1 → 5.5.2 5.5.3 6.0.0 6.0.1 6.0.2 6.0.3 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
5.5.2 → 5.5.3 6.0.0 6.0.1 6.0.2 6.0.3 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
5.5.3 → 6.0.0 6.0.1 6.0.2 6.0.3 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.0 → 6.0.1 6.0.2 6.0.3 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.1 → 6.0.2 6.0.3 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.2 → 6.0.3 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.3 → 6.0.4 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.4 → 6.0.5 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.5 → 6.0.6 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.6 → 6.0.7 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.7 → 6.0.8 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.0.8 → 6.1.0 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.1.0 → 6.1.1 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.1.1 → 6.1.2 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.1.2 → 6.2.0 6.2.1 6.2.2 6.2.3 6.3.0
6.2.0 → 6.2.1 6.2.2 6.2.3 6.3.0
6.2.1 → 6.2.2 6.2.3 6.3.0
6.2.2 → 6.2.3 6.3.0
6.2.3 → 6.3.0
Rolling Upgrade Supported
Rolling upgrades for HA environments using embedded RabbitMQ and/or embedded Elasticsearch services are not supported
Non-Rolling Upgrade Supported
Upgrade Not Recommended*
Upgrade Not Supported
Downgrade Not Supported

* Some Features and Fixes in the From version may not be included in the To version due to From version being released after the To version.

  • 4.2.0 to 5.0.0 Appliances require upgrade to 5.2.x or 5.3.x prior to upgrading to 5.4.x+



Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, HPE OneView, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.


Supported Version(s)



2.7.x or higher

Ansible Tower


App Dynamics


Azure Stack

2002 back to 1908

2019-03-01-hybrid api-profile version used which is supported in 1908 and later Azure Stack versions

Cisco ACI


Citrix Netscaler



v11 sp 19

F5 Big-IP



Latest Versions Supported



Microsoft Hyper-V

2012R2, 2016, 2019

Nutanix AHV

5.0 - 5.10 Note: Prism Central is not a supported endpoint

In 5.5 - 5.7 if Prism Central is managing Prism Element, image creation will not function due to PC Image Management.


Latest Versions Supported

When creating an OpenStack integration, select the latest available from the OS Version dropdown menu when running a later version



Puppet Agent version will be latest 6 version from yum.puppetlabs.com or apt.puppetlabs.com


Up to 7.x


2016, 2019


Orlando, Paris, Quebec, Rome


v0.11.x, v0.12.18+, 0.13.x, 0.14.x, 1.1.x, 1.2.x

vCloud Director

10.0, 10.2, 10.3, 10.4

When upgrading a vCD environment, you should update the API Version setting on the Morpheus Cloud configuration first


10, 11

VMware ESXi

6.5, 6.7, 7, 8

VMware Fusion

8, 9, 10+

VMware NSX

-T (up to 3.1.3.x)

VMware vCenter

5.5, 6.0, 6.5, 6.7, 7.x, 8.x






Non-listed versions may be compatible but are not verified.