Bug 1290871

Summary:	heat-manage purge_deleted doesn't
Product:	Red Hat OpenStack	Reporter:	Dan Yocum <dyocum>
Component:	openstack-heat	Assignee:	Ryan Brown <rybrown>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Amit Ugol <augol>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	dyocum, mburns, rhel-osp-director-maint, sbaker, shardy, yeylon
Target Milestone:	---
Target Release:	8.0 (Liberty)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-22 17:35:04 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:

Description Dan Yocum 2015-12-11 18:04:24 UTC

Description of problem:

$subject

Here's what I'm runninng:

heat-manage purge_deleted -g seconds 60

The heat.raw_template table doesn't change - it remains the same size with the same number of entries.

minutes, hours and days.

There is no deleted_at field in this table - how is the state of 'deleted' determined?

Version-Release number of selected component (if applicable):


openstack-heat-common-2015.1.1-7.el7ost.noarch

How reproducible:

Every


Steps to Reproduce:
1. deploy overcloud
2. delete overcloud
3. run 'heat manage purge_deleted -g minutes 1'

Actual results:

Nothing is deleted, table stays the same size

Expected results:

heat.raw_template gets purged of deleted templates



Additional info:

Comment 2 Zane Bitter 2015-12-11 19:23:20 UTC

purge_deleted works on the stack table, that's the one that has deleted_at. Purging that table should clear all of the associated raw_template entries (as well as resources, events, and so on). If there are raw_template entries being left behind, it could be either because the deleted stacks are not being purged or because raw_template entries are leaking (i.e. there are raw_templates not referenced by stacks).

It's quite possibly the former, though, because this bug:

https://bugs.launchpad.net/heat/+bug/1439518

was backported upstream between 2015.1.1 and 2015.1.2. Can you try again with the latest version of Heat? There is a good chance this is already fixed.

Comment 3 Dan Yocum 2015-12-21 14:27:27 UTC

Zane - I'm sticking with GA, not installing from a puddle - when will 2015.1.2 be available?

Comment 4 Dan Yocum 2015-12-22 17:35:04 UTC

10/10 can confirm, now.  2015.1.2 fixes this problem.  Closing this BZ.