Bug 1381161

Summary: BootstrapTreeview trees glitching sometimes.
Product: Red Hat CloudForms Management Engine Reporter: Milan Falešník <mfalesni>
Component: UI - OPSAssignee: Dávid Halász <dhalasz>
Status: CLOSED WORKSFORME QA Contact: Milan Falešník <mfalesni>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7.0CC: dajohnso, hkataria, jhardy, mfalesni, mpovolny, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: automate:ui
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-16 10:58:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:

Description Milan Falešník 2016-10-03 09:38:21 UTC 
Description of problem:
Sometimes when you work on screens that include the BootstrapTreeview, the tree "breaks" and no longer reacts to clicks. By going away and returning it is possible to remove this problem and work normally until it happens again.

I started seeing this in 5.7 earlier but could not find a 100% reproducer. This one that I will describe seems to work somehow.

Version-Release number of selected component (if applicable):
5.7 (currently reproduced on 5.7.0.3

How reproducible:
not 100%

Steps to Reproduce:
1. Have a domain and copy an instance there (there will be a glitch from earlier BZ that will block you on the copy screen, but you can navigate away and come back and it works)
2. Edit the instance. Change anything. Save it.
3. Select an another node in the tree.

Actual results:
Nothing happens. Nothing in the dev console in the browser. When you go away and return back, the functionality is restored until it breaks again.

Expected results:
Once you click a tree node, spinner appears and another screen appears.

Additional info:
You may need to try it a couple of times, or you might face it sooner than step 3) in the steps.