Bug 1456787

Summary:	Embedded ansible fails to initialize after backup/restore
Product:	Red Hat CloudForms Management Engine	Reporter:	luke couzens <lcouzens>
Component:	Appliance	Assignee:	Gregg Tanzillo <gtanzill>
Status:	CLOSED DUPLICATE	QA Contact:	luke couzens <lcouzens>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.8.0	CC:	abellott, cpelland, jhardy, ncarboni, obarenbo, yrudman
Target Milestone:	GA
Target Release:	5.8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ansible_embed:black
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-05 18:05:11 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:

Comment 2 Nick Carboni 2017-05-30 13:31:13 UTC

This one is failing because we create the default objects on the ansible side, but then don't backup and restore that database.

This is leaving us in an odd situation where the embedded ansible database is in a state from after the backup was taken, but we've restored the backup to the vmdb database.

This causes the embedded ansible worker to think that it hasn't created the objects remotely yet.

This could be fixed by https://github.com/ManageIQ/manageiq/pull/14508 which will use existing objects in the awx database as our default objects if they exist.

But I suspect that the "correct" solution would be to backup both the awx and vmdb databases at the same time.

Comment 3 Yuri Rudman 2017-07-05 18:05:11 UTC

Closing thi BZ since instructions to perform a full binary backup of the entire DB server are in https://bugzilla.redhat.com/show_bug.cgi?id=1459652

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