Project

General

Profile

Actions

Bug #55623

closed

cephadm: call handling causing process to not exit when container does

Added by Adam King almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
quincy
Regression:
Yes
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Basically, in certain environments with certain commands (specifically saw on a host with 102 multipath devices, running a `cephadm ceph-volume inventory` command), when cephadm runs a subprocess like `podman run . . .` we're seeing situations where the command in the container will complete, the container will exit but the actual process for the `podman run` command does not. This causes cephadm to hang indefinitely waiting for the process to finish.

This seems to be caused by a recent change to the `call` function in the cephadm binary as reverting the change locally caused the issue to go away.


Related issues 1 (0 open1 closed)

Related to Orchestrator - Bug #55265: cephadm hangs forever if the mon cannot bind on the provided port (--mon-addrv)Won't FixRedouane Kachach Elhichou

Actions
Actions #1

Updated by Redouane Kachach Elhichou almost 2 years ago

  • Related to Bug #55265: cephadm hangs forever if the mon cannot bind on the provided port (--mon-addrv) added
Actions #2

Updated by Adam King almost 2 years ago

  • Status changed from New to Resolved
  • Backport set to quincy
  • Pull request ID set to 46245
Actions

Also available in: Atom PDF