Bug #55466: systemctl stop for ceph services fails with a "no such container" error - Orchestrator - Ceph

Actions

Copy link

Bug #55466

closed

systemctl stop for ceph services fails with a "no such container" error

Added by Redouane Kachach Elhichou about 2 years ago. Updated almost 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Redouane Kachach Elhichou

Category:

cephadm

Target version:

% Done:

Source:

Tags:

Backport:

quincy

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

46054

Crash signature (v1):

Crash signature (v2):

Description

This error happens when stopping any service. For example stopping grafana:

root@ceph-node-0 ~]# systemctl status ceph-ab518472-c602-11ec-92a8-525400879096@grafana.ceph-node-0.service
...
...
Apr 27 11:28:41 ceph-node-0 bash[85452]: ceph-ab518472-c602-11ec-92a8-525400879096-grafana-ceph-node-0
Apr 27 11:28:41 ceph-node-0 bash[85511]: Error: no container with name or ID "ceph-ab518472-c602-11ec-92a8-525400879096-grafana.ceph-node-0" found: no such container
Apr 27 11:28:41 ceph-node-0 systemd[1]: ceph-ab518472-c602-11ec-92a8-525400879096@grafana.ceph-node-0.service: Deactivated successfully.

The unit.stop script use to stop the service is:

[root@ceph-node-0 ~]# cat /var/lib/ceph/ab518472-c602-11ec-92a8-525400879096/grafana.ceph-node-0/unit.stop 
! /usr/bin/podman stop ceph-ab518472-c602-11ec-92a8-525400879096-grafana-ceph-node-0
! /usr/bin/podman stop ceph-ab518472-c602-11ec-92a8-525400879096-grafana.ceph-node-0