Forceful removal of containers in paunch/tripleo-container-manage leaves leftovers behind
Bug #1860004 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Bogdan Dobrelya |
Bug Description
Paunch does docker/podman rm -f, when removes containers. It seems it
returns too early, having some leftovers (like docker service
endpoints) behind or pending for it to be removed later, in case of
big fat deamons.
Long story short, don't do rm -f and allow it to do its job gracefully
and without a hurry.
Changed in tripleo: | |
importance: | Undecided → High |
milestone: | none → ussuri-2 |
tags: | added: queens-backport-potential |
tags: | added: train-backport-potential |
Changed in tripleo: | |
status: | In Progress → Triaged |
status: | Triaged → In Progress |
summary: |
- Forceful removal of containers in paunch leaves leftovers behind + Forceful removal of containers in paunch/tripleo-container-manage leaves + leftovers behind |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/702899
Review: https:/