volume may not be deleted during destroy

Bug #1636182 reported by Jeffrey Zhang on 2016-10-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Undecided
Unassigned

Bug Description

now, docker volumes, which is used by kolla deployed containers, are removed. This could be wrong in some case when volume is created specifically and error happens before it is used by containers. Then this volume will never be removed by destroy script.

Changed in kolla:
milestone: none → ocata-1
importance: Undecided → Medium
description: updated
Changed in kolla:
assignee: nobody → Surya Prakash Singh (confisurya)
Changed in kolla:
milestone: ocata-1 → ocata-2
Changed in kolla:
status: New → Confirmed
Changed in kolla:
milestone: ocata-2 → ocata-3
Christian Berendt (berendt) wrote :

Removed assignee because he is not working on this bug.

Changed in kolla:
assignee: Surya Prakash Singh (confisurya) → nobody

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
importance: Medium → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers