Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1691839

Summary: [OSP15][Deployment] Volumes remain in the attached state even when the instance is already deleted
Product: Red Hat OpenStack Reporter: Martin Schuppert <mschuppe>
Component: openstack-tripleo-heat-templatesAssignee: Rajesh Tailor <ratailor>
Status: CLOSED ERRATA QA Contact: Archit Modi <amodi>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: amodi, dasmith, eglynn, gregraka, jhakimra, kchamart, lyarwood, mbooth, mburns, nova-maint, ratailor, sbauza, schhabdi, sgordon, vromanso
Target Milestone: betaKeywords: Triaged, ZStream
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-nova-14.4.1-0.20190529171754.f30766c.el8ost puppet-tripleo-10.4.2-0.20190531190405.7559e63.el8ost openstack-tripleo-heat-templates-10.5.1-0.20190603084723.152e465.el8ost Doc Type: Bug Fix
Doc Text:
In earlier releases of Red Hat OpenStack Platform, when these conditions were true: - The option, reclaim_instance_interval, was greater than zero. - The option, delete_on_termination, was set to true. - The instance which is booted from the volume was deleted. Then, after the "reclaim_instance_interval" passed, the volume on which the instance was booted, incorrectly displayed a status of "attached" and "in-use". In RHOSP 15, the workaround is to do the following: 1. In the Compute service configuration file, nova.conf, add a user/project configuration to the group, cinder. 2. When the context is is_admin, connect to the Block Storage service (cinder) API, authenticating with nova.conf and without using a token.
 Story Points: ---
Clone Of: 1691324
: 1691840 1691842 1691844 (view as bug list) Environment:
Last Closed: 2019-09-21 11:20:58 UTC Type: ---
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: 1691840, 1691842, 1691844    

Comment 14 errata-xmlrpc 2019-09-21 11:20:58 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/RHEA-2019:2811