Bug 1353233
| Summary: | ManageIQ Automate domain cleanup | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
| Component: | Automate | Assignee: | Greg McCullough <gmccullo> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Falešník <mfalesni> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.6.0 | CC: | cpelland, dajohnso, gmccullo, jhardy, mkanoor, mmojzis, obarenbo, tfitzger |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.6.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | automate | ||
| Fixed In Version: | 5.6.1.2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1287891 | Environment: | |
| Last Closed: | 2016-08-18 17:55:22 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: | 1287891 | ||
| Bug Blocks: | 1288150 | ||
|
Comment 2
John Prause
2016-07-06 15:11:36 UTC
Checked in 5.6.1.0
I copied the fixtures in domfix directory, unzipped the export in domexp directory. I turned all dirnames and filenames lowercase and then diffed it.
Apart of the manifest file which I ignore because it only contains hashes and dates, I see only one difference:
diff -aurN domfix/manageiq/__domain__.yaml domexp/manageiq/__domain__.yaml
--- domfix/manageiq/__domain__.yaml 2016-08-01 07:46:26.238227097 -0400
+++ domexp/manageiq/__domain__.yaml 2016-08-01 05:59:38.000000000 -0400
@@ -9,3 +9,4 @@
system: true
priority: 0
enabled: true
+ tenant_id: 1
I guess that tenant id is ok as it gets assigned upon loading the fixtures into the database, right?
That is correct. We retain the tenant_id for the restore operation but a normal import would re-assign. Verified it be then. 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://rhn.redhat.com/errata/RHSA-2016-1634.html |