Description of problem: Resetting the default automate domains does not retain the order of the domain. The ManageIQ domain is always set a the first domain, but other domains, like RedHat, get added as the last domain.
Version-Release number of selected component (if applicable): 5.3.x
Steps to Reproduce:
1. Have the Redhat domain available along with at least 1 other user domain which has a higher priority than the Redhat domain.
2. In the UI goto Automate -> Import/Export -> "Reset all Datastore custom classes and instances to default"
Actual results: The RedHat domain will become the highest priority domain.
Expected results: The RedHat domain should maintain the same domain order as before the reset.
New commit detected on manageiq/master:
Author: Madhu Kanoor <firstname.lastname@example.org>
AuthorDate: Tue Mar 17 15:23:58 2015 -0400
Commit: Madhu Kanoor <email@example.com>
CommitDate: Wed Mar 18 10:01:12 2015 -0400
Preserve & set the priority,enabled,system of domains after db reset
vmdb/app/models/miq_ae_datastore.rb | 11 +++++++++++
1 file changed, 11 insertions(+)
Checked in 126.96.36.199.19, the domains keep their order and the ManageIQ domain is not allowed to be moved.
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.