Description of problem: The Automate DB uses YAML files to store the domain, namespace, class, instance and methods on the disk under db/fixtures/ae_datastore/ManageIQ. Some of these YAML files were hand edited leading to inconsistencies and also incorrect names of YAML files. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Export the ManageIQ domain 2. Compare the Exported data with the YAML files on the disk. 3. Actual results: Expected results: The exported data should match the data in the YAML files Additional info:
Fixed in PR https://github.com/ManageIQ/manageiq/pull/5649
I have found, that there are folders, which have different names. For example: ManageIQ/System/Event/EmsEvent/OPENSTACK.class in db fixture ManageIQ/System/Event/EmsEvent/OpenStack.class in exported domain Should it be case sensitive or not?
You should look at the internal name in the __class__.yaml file. Typically everything in Automate Name search is case insensitive If the __class__.yaml has a different name from the folder, it might make sense to make them consistent.
Okay, still found some differences. More in attachment.
Created attachment 1160981 [details] differencies
https://github.com/ManageIQ/manageiq/pull/9089
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/236bc8f86b878eada54c39ef1a1ac0f74ffff820 commit 236bc8f86b878eada54c39ef1a1ac0f74ffff820 Author: Madhu Kanoor <mkanoor> AuthorDate: Wed Jun 1 12:21:04 2016 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Wed Jun 1 12:21:04 2016 -0400 Cleanup ManageIQ domain https://bugzilla.redhat.com/show_bug.cgi?id=1287891 .../StateMachine/Deployment.class/__class__.yaml | 20 +- .../ContainerProvider/__namespace__.yaml | 10 +- .../Event/EmsEvent/GOOGLE.class/__class__.yaml | 600 ++++++++++----------- .../Event/EmsEvent/GOOGLE.class/_missing.yaml | 6 +- .../GOOGLE.class/compute_instances_delete.yaml | 6 +- .../GOOGLE.class/compute_instances_insert.yaml | 6 +- .../GOOGLE.class/compute_instances_start.yaml | 6 +- .../GOOGLE.class/compute_instances_stop.yaml | 6 +- 8 files changed, 330 insertions(+), 330 deletions(-)
https://github.com/ManageIQ/manageiq/pull/9133
https://github.com/ManageIQ/manageiq/pull/7620
Matous Have you gotten a chance to test this? Thanks, Madhu
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/RHBA-2016:1348
Provided Info to QE