Actions
Bug #55623
closedcephadm: call handling causing process to not exit when container does
% Done:
0%
Source:
Tags:
Backport:
quincy
Regression:
Yes
Severity:
2 - major
Reviewed:
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.
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
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