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

Bug 1778905

Summary:	Update nova database archive cron job to use --all-cells
Product:	Red Hat OpenStack	Reporter:	melanie witt <mwitt>
Component:	openstack-tripleo-heat-templates	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Paras Babbar <pbabbar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16.0 (Train)	CC:	mburns, mschuppe, pbabbar
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:	2019-12-04 09:20:26 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:	1703091
Bug Blocks:

Description melanie witt 2019-12-02 18:41:20 UTC

This bug was initially created as a copy of Bug #1703091

I am copying this bug because: 

A new --all-cells option was added to 'nova-manage db archive_deleted_rows' and it needs to be able to be specified in the database archive cron job. 

Description of problem:
Since we're using nova_cell0 instead of nova database, nova-manage db archive_deleted_rows is no longer archiving deleted rows

nova-manage db archive_deleted_rows --verbose --max_rows 1000000

Version-Release number of selected component (if applicable):
# rpm -qa|grep nova
python-nova-17.0.5-3.d7864fbgit.el7ost.noarch
openstack-nova-api-17.0.5-3.d7864fbgit.el7ost.noarch
puppet-nova-12.4.0-6.el7ost.noarch
openstack-nova-common-17.0.5-3.d7864fbgit.el7ost.noarch
python2-novaclient-10.1.0-1.el7ost.noarch

How reproducible:
Always

Steps to Reproduce:
1. Get 705k deleted instances
2. run nova-manage db archive_deleted_rows
3.

Actual results:
Nothing is archived

Expected results:
All rows should be achived up to --max_rows

Additional info:

Comment 1 Martin Schuppert 2019-12-04 09:20:26 UTC


*** This bug has been marked as a duplicate of bug 1778814 ***