Mirantis OpenStack

cinder volume deletions-in-progress lead to stack deletion errors

  1. Series 6.0.x
  2. Bug #1550454
Bug #1550454 reported by Dmitry Sutyagin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
High
MOS Maintenance
Mirantis OpenStack 8.0-updates
6.0.x
Fix Committed
High
Rodion Tikunov
Mirantis OpenStack 6.0-updates
6.1.x
Fix Released
High
Rodion Tikunov
Mirantis OpenStack 6.1-mu-6
7.0.x
Invalid
High
MOS Maintenance
Mirantis OpenStack 7.0-updates
8.0.x
Invalid
High
MOS Maintenance
Mirantis OpenStack 8.0-updates

Bug Description

We need to backport the fix from the upstream bug - https://bugs.launchpad.net/heat/+bug/1362708 to MOS 6.0

Dmitry Sutyagin (dsutyagin)
Changed in mos:
milestone: none → 6.0-updates
assignee: nobody → MOS Maintenance (mos-maintenance)
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to openstack/heat (openstack-ci/fuel-6.1/2014.2)

Fix proposed to branch: openstack-ci/fuel-6.1/2014.2
Change author: Rakesh H S <email address hidden>
Review: https://review.fuel-infra.org/17756

Revision history for this message
Rodion Tikunov (rtikunov) wrote :

The bug fixed since 7.0 and have not reproduced in the lab.

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to openstack/heat (openstack-ci/fuel-6.0-updates/2014.2)

Reviewed: https://review.fuel-infra.org/17574
Submitter: Vitaly Sedelnik <email address hidden>
Branch: openstack-ci/fuel-6.0-updates/2014.2

Commit: 146b77cf22f13b4bdb57edd6e7c89f370d4d55a4
Author: Rakesh H S <email address hidden>
Date: Thu Mar 3 13:45:22 2016

fixes stack deletion failure, when vol in deleting

when an delete operation is requested on a stack, and the volume in stack
is already in 'deleting' state, heat fails to delete the stack and goes to
DELETE_FAILED state instantly.

Instead of going to DELETE_FAILED state instantly, heat needs to safely
wait for the volume to complete its deletion process, so that heat can
then go ahead and complete stack deletion successfully.

Closes-Bug: #1550454

Change-Id: I088eab90bee4bc804abe9e505fd61b17b266def1
(cherry picked from commit 6aca29e05bb0cfe469ed17f4ab9bb9351b2f108a)

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to openstack/heat (openstack-ci/fuel-6.1/2014.2)

Reviewed: https://review.fuel-infra.org/17756
Submitter: Vitaly Sedelnik <email address hidden>
Branch: openstack-ci/fuel-6.1/2014.2

Commit: f60f3560d65244c23a525fc060c97b3dda82cd38
Author: Rakesh H S <email address hidden>
Date: Fri Mar 4 09:53:37 2016

fixes stack deletion failure, when vol in deleting

when an delete operation is requested on a stack, and the volume in stack
is already in 'deleting' state, heat fails to delete the stack and goes to
DELETE_FAILED state instantly.

Instead of going to DELETE_FAILED state instantly, heat needs to safely
wait for the volume to complete its deletion process, so that heat can
then go ahead and complete stack deletion successfully.

Closes-Bug: #1550454

Change-Id: I088eab90bee4bc804abe9e505fd61b17b266def1
(cherry picked from commit 6aca29e05bb0cfe469ed17f4ab9bb9351b2f108a)

Dmitry Belyaninov (dbelyaninov)
tags: added: on-verification
Revision history for this message
Dmitry Belyaninov (dbelyaninov) wrote :

Verified on MOS 6.1 + mu6 updates.

Described scenario works fine.

tags: removed: on-verification
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.