Description of problem: When you navigate to Automate, Import/Export you can click on "Reset all Datastore custom classes and instances to default" - although it says so, it only resets the ManageIQ and Red Hat domain and doesn't touch any custom domains. This was true when we didn't have the multiple domains in very old versions. Version-Release number of selected component (if applicable): 5.6, but earlier versions too How reproducible: always Steps to Reproduce: 1. navigate to Automate, Export/Import 2. Reset all Datastore custom classes and instances to default 3. Actual results: It actually doesn't reset the "custom classes", it only reset the ManageIQ and Red Hat Domains - it doesn't change anything on custom (aka. user created) domains. Expected results: The text should be less confusing Additional info: it's not obvious you have to click on the arror icon to actually perform this action. There should be an easy to identify button.
Suggested change: "Reset all components in the following domains: XXX, YYY" We will need a method in the MiqAeDatastore model to return the names which need to be read from the YAML files stored in fixtures/ae_datastore directory.
Patrik - I would like to refactor the code in reset_to_defaults to create a new method that yields the domain_file. This new method can then be used in reset_to_defaults as well as a new method that returns the Domain name that is stored in the domain_file (which is yaml). The code I am referring to is here: https://github.com/ManageIQ/manageiq/blob/master/lib/miq_automation_engine/models/miq_ae_datastore.rb#L167
solved in PR: https://github.com/ManageIQ/manageiq/pull/10899
*** Bug 1373996 has been marked as a duplicate of this bug. ***
Verified in 5.7.0.1 The text is now more descriptive.
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/RHBA-2017-0012.html