This document is for a development version of Ceph.

Upgrading Ceph

Cephadm is capable of safely upgrading Ceph from one bugfix release to another. For example, you can upgrade from v15.2.0 (the first Octopus release) to the next point release v15.2.1.

The automated upgrade process follows Ceph best practices. For example:

  • The upgrade order starts with managers, monitors, then other daemons.

  • Each daemon is restarted only after Ceph indicates that the cluster will remain available.

Keep in mind that the Ceph cluster health status is likely to switch to HEALTH_WARNING during the upgrade.

Starting the upgrade

Before you begin using cephadm to upgrade Ceph, verify that all hosts are currently online and that your cluster is healthy:

ceph -s

To upgrade (or downgrade) to a specific release:

ceph orch upgrade start --ceph-version <version>

For example, to upgrade to v15.2.1:

ceph orch upgrade start --ceph-version 15.2.1

Monitoring the upgrade

Determine whether an upgrade is in process and what version the cluster is upgrading to with:

ceph orch upgrade status

While the upgrade is underway, you will see a progress bar in the ceph status output. For example:

ceph -s

Expected output:

    Upgrade to (00h 20m 12s)
      [=======.....................] (time remaining: 01h 43m 31s)

You can also watch the cephadm log by running the following command:

ceph -W cephadm

Canceling an upgrade

You can stop the upgrade process at any time with:

# ceph orch upgrade stop

Potential problems

There are a few health alerts that can arise during the upgrade process.


This alert means that Ceph requires an active and standby manager daemon in order to proceed, but there is currently no standby.

You can ensure that Cephadm is configured to run 2 (or more) managers by running the following command:

ceph orch apply mgr 2  # or more

You can check the status of existing mgr daemons by running the following command:

ceph orch ps --daemon-type mgr

If an existing mgr daemon has stopped, you can try to restart it by running the following command:

ceph orch daemon restart <name>


This alert means that Ceph was unable to pull the container image for the target version. This can happen if you specify a version or container image that does not exist (e.g. “1.2.3”), or if the container registry can not be reached by one or more hosts in the cluster.

To cancel the existing upgrade and to specify a different target version, run the following commands:

ceph orch upgrade stop
ceph orch upgrade start --ceph-version <version>

Using customized container images

For most users, upgrading requires nothing more complicated than specifying the Ceph version number to upgrade to. In such cases, cephadm locates the specific Ceph container image to use by combining the container_image_base configuration option (default: with a tag of vX.Y.Z.

But it is possible to upgrade to an arbitrary container image, if that’s what you need. For example, the following command upgrades to a development build:

ceph orch upgrade start --image

For more information about available container images, see Ceph Container Images.