Bug 1548070

Summary: Heat is not shutting down instances before anything else when running a stack-delete
Product: Red Hat OpenStack Reporter: David Vallee Delisle <dvd>
Component: openstack-heatAssignee: Zane Bitter <zbitter>
Status: CLOSED NOTABUG QA Contact: Ronnie Rasouli <rrasouli>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: jmelvin, marjones, mburns, rhel-osp-director-maint, sbaker, shardy, srevivo, therve, zbitter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-15 14:14:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vm with volume as root disk none

Description David Vallee Delisle 2018-02-22 16:08:49 UTC 
Description of problem:
Having the instances running when detaching volume generates issues as described in these BZ: bug 1548053 bug 1546826


Version-Release number of selected component (if applicable):
openstack-heat-common-9.0.1-3

How reproducible:
100% of the time

Steps to Reproduce:
1. Create a stack with running instances
2. Delete stack with running instances

Actual results:
If the volumes are in use in the instances, libvirt is unable to cleanly detach them, thus failing the stack-delete

Expected results:
stack-delete shouldn't fail

Additional info:
If heat would shutdown the instance before, all the volume detachment would work
Comment 2 Zane Bitter 2018-03-05 16:32:55 UTC 
So IIUC this is believed to be a regression in libvirt, but you want Heat to work around it?

Seeing the template would help. Are you using a separate VolumeAttachment resource, or attaching it directly to the server?

If the former then there's definitely nothing Heat can do. If the latter then it might be possible, I guess, but I'd still be concerned that it's a fairly substantial behaviour change to address a problem that is not of Heat's making, and which will in any event continue to exist for any users of Cinder that either don't use Heat or use the VolumeAttachment resource.
Comment 3 Jeremy 2018-03-05 17:01:23 UTC 
Created attachment 1404407 [details]
vm with volume as root disk