Bug 1349113

Summary:	Resetting the default automate domains does not retain the domain order
Product:	Red Hat CloudForms Management Engine	Reporter:	Colin Arnott <carnott>
Component:	Automate	Assignee:	mkanoor
Status:	CLOSED WORKSFORME	QA Contact:	Milan Falešník <mfalesni>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.5.0	CC:	benglish, cpelland, dajohnso, gmccullo, hkataria, jhardy, mfalesni, mkanoor, mpovolny, obarenbo, tfitzger
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	automate
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1353645 (view as bug list)		Environment:
Last Closed:	2017-05-11 09:23:20 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:
Bug Blocks:	1353645

Description Colin Arnott 2016-06-22 17:46:13 UTC

Description of problem:
Resetting the default automate domains does not retain the order of the domains in the accordion, immediately after the reset.  The ManageIQ domain is always set a the first domain, but other domains, like RedHat, get added as the last domain, above other custom domains.

Note: it does look like this goes away after some time (logout, timeout, refresh, etc.)

Version-Release number of selected component (if applicable):
cfme-5.5.4.2-1.el7cf.x86_64

How reproducible:
tricky, or harder

Steps to Reproduce:
0. import/create custom automate domain
1. see warning about:
 a. CloudForms domain: Current version - 5.5.3.4, Available version - 5.5.4.2
 b. ManageIQ domain: Current version - 5.5.3.4, Available version - 5.5.4.2
2. Reset all Datastore custom classes and instances to default

Actual results:
The RedHat domain will become the highest priority domain on the accordion.

Expected results:
The RedHat domain should maintain the same domain order as before the reset.

Additional info:
I attempted to reproduce this on another appliance, but was unable.

Comment 3 Greg McCullough 2016-07-07 16:01:11 UTC

Resetting bug component back to Automate.

Comment 5 mkanoor 2016-07-08 18:27:53 UTC

Is the reset being done from the UI or from the rails console using the rake command.

Comment 6 Colin Arnott 2016-07-11 10:55:41 UTC

It is being done from the webUI

Comment 7 mkanoor 2016-07-11 16:51:35 UTC

Colin,
When you do it from the UI, I think it runs as a background task, is it possible that there is some timing bug that doesn't cause it to refresh the UI right away. The Import/Export/Restore UI screen is different from the Explorer tree screen switching between the trees is going to cause the entire tree to be refreshed.
Did you wait for the restore to finish before you switched to the Explorer tree view?
Thanks,
Madhu

Comment 8 Colin Arnott 2016-07-13 11:22:51 UTC

Yes, when testing I imported two automate domains, they finished successfully, then I went back to Automate → Explorer

--
Colin Arnott

Comment 9 mkanoor 2016-10-10 21:16:02 UTC

Colin,
I haven't been able to reproduce this. Have you seen this happen again?
If not can we close this issue and reopen it once we can recreate it.

Thanks,
Madhu

Comment 11 mkanoor 2017-04-17 15:57:46 UTC

Haven't been able to reproduce this, I think we should lower the PM score on this.

Comment 13 Dave Johnson 2017-04-17 16:46:24 UTC

Milan, can you please re-test this and determine if there is a problem here.

Comment 14 Milan Falešník 2017-04-18 15:18:31 UTC

I have just tried it on 5.8.0.10 and it did not happen. I have created a couple of custom domains which I distributed around the redhat domain and it did not move.

Though the button says:
Reset all components in the following domains: ManageIQ

So it is probably not touching the RedHat domain at all.

Comment 15 mkanoor 2017-05-10 20:48:48 UTC

Milan/Dave can we close this and reopen it if need be.