Ceph OSD service for removed OSD tries to start after running ceph-ansible playbook
Issue
- After removing one or more OSD from a Ceph cluster using instructions from the OpenStack Documentation, running an overcloud deploy or ceph-ansible playbook will cause the destroyed OSD service to re-enable and try to restart.
- Ceph OSD systemd service will be enabled for an OSD that does not exist
- Ceph OSD containers will repeatedly start and stop for destroyed OSDs
- OpenStack overcloud deployment may fail while inspecting containers or while trying to restart OSDs.
Environment
- Red Hat Ceph Storage 4.x
- OpenStack 16.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
