Bug 1631358

Summary: Volumes created externally can't be detached properly on update
Product: Red Hat OpenStack Reporter: Thomas Hervé <therve>
Component: openstack-heatAssignee: Rabi Mishra <ramishra>
Status: CLOSED ERRATA QA Contact: Victor Voronkov <vvoronko>
Severity: medium Docs Contact:
Priority: low    
Version: 10.0 (Newton)CC: ahrechan, mburns, pmorey, ramishra, sbaker, shardy, vvoronko
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-heat-7.0.6-5.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1637423 1637424 1637425 1637426 (view as bug list) Environment:
Last Closed: 2019-01-16 17:10:40 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:
Bug Depends On:    
Bug Blocks: 1637423, 1637424, 1637425, 1637426    

Description Thomas Hervé 2018-09-20 12:08:22 UTC 
If you pass a volume ID as a stack parameter to be used for a OS::Cinder::VolumeAttachment resource, any server replacement will cause the stack to hang.

The reason is that when we detach the volume, we then check if the volume is available. But at that point, the volume has already been reattached to the other server, so we spin forever waiting for the status to change.

The workaround is to use block_device_mapping instead, or to manage the volume in the stack (I think?).
Comment 13 Artem Hrechanychenko 2018-11-14 10:24:24 UTC 
That bz was already assigned and Rabi is working on it. no reasons for me to assign it to a DFG:DF
moving to cloud-apps
Comment 23 Victor Voronkov 2018-12-12 12:05:13 UTC 
Verified on puddle 2018-12-04.1
Comment 25 errata-xmlrpc 2019-01-16 17:10:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0076