Updating Red Hat OpenStack Platform 13. z12 and earlier with Ceph Storage might fail during controller update

Solution In Progress - Updated -

Issue

  • If you use Red Hat Ceph Storage 3.3 z5 or earlier in your Red Hat OpenStack Platform environment and run openstack overcloud update run --nodes Controller, the update might fail with the following error:
 TASK [Stop mons to make them consistent with systemd] **************************
  2022-02-25 04:21:34 | Friday 25 February 2022  04:21:33 +0000 (0:00:00.450)       0:05:54.143 *******
  2022-02-25 04:21:34 | fatal: [controller-2]: FAILED! => {"changed": true, "cmd": "docker stop ceph-mon-controller-2", "delta": "0:00:00.040103", "end": "2022-02-25 04:21:33.802947", "msg": "non-zero return code", "rc": 1, "start": "2022-02-25 04:21:33.762844", "stderr": "Error response from daemon: No such container: ceph-mon-controller-2", "stderr_lines": ["Error response from daemon: No such container: ceph-mon-controller-2"], "stdout": "", "stdout_lines": []}
  2022-02-25 04:21:34 |
  • If you have ceph-mon and ceph-mgr services (on Controllers by default) that do not have the docker systemd service dependency, run the following command to verify whether the systemd services include dependency(Requires option):
grep -i "Requires=docker.service" /etc/systemd/system/ceph-m*\@.service

Environment

  • Red Hat OpenStack Platform 13. z12 and earlier
  • Red Hat Ceph Storage 3.3 z5 and earlier

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content