Bug 1287858 - containers: No Class found for explorer tree node id '12-' [container/explorer]
Summary: containers: No Class found for explorer tree node id '12-' [container/explorer]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: GA
: 5.5.2
Assignee: Daniel Korn
QA Contact: Einat Pacifici
URL:
Whiteboard: container
Depends On: 1286247 1294374 1295430
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 20:47 UTC by John Prause
Modified: 2016-02-10 15:21 UTC (History)
10 users (show)

Fixed In Version: 5.5.2.1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1286247
Environment:
Last Closed: 2016-02-10 15:21:19 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0159 0 normal SHIPPED_LIVE CFME 5.5.2 bug fixes and enhancement update 2016-02-10 20:19:02 UTC

Description John Prause 2015-12-02 20:47:29 UTC
+++ This bug was initially created as a clone of Bug #1286247 +++

Description of problem:

selecting timeline for containers -> timeline pods -> containers causes:
No Class found for explorer tree node id '12-' [container/explorer] 

Version-Release number of selected component (if applicable):

cfme-5.5.0.12-rc2.1.el7cf.x86_64

How reproducible:

100%

Steps to Reproduce:
1. select containers -> containers -> first container 
2. select monitoring -> timelines
3. select containers -> pods 
4. select monitoring -> timelines
5. select containers -> containers

Actual results:

1. we get an exception: No Class found for explorer tree node id '12-' [container/explorer] 
2. we have to logout -> login to be able to view containers again

Expected results:

We should not get an exception.
we should not have to logout ->login to view containers again. 

Additional info:


Unexpected error encountered

Errors in Management Engine can be caused by:

① Accessing Management Engine from multiple tabs or windows of the same browser on a single machine. Close any duplicate browser sessions, then select a menu option above.
② Pressing the back button during a session.
      Close any duplicate browser sessions, then select a menu option above.
③ An internal system error.
      Please contact your administrator for assistance.


Error text:

No Class found for explorer tree node id '12-' [container/explorer]

--- Additional comment from Federico Simoncelli on 2015-11-30 06:12:42 EST ---

This is a UI bug but the logs attached are the backend ones. Dafna please attach the production.log as well (you should see the stacktrace there).

--- Additional comment from Dafna Ron on 2015-11-30 06:39 EST ---



--- Additional comment from Daniel Korn on 2015-11-30 07:01:08 EST ---

There should be another step: "select a random pod" between 3 and 4, right Dafna (I was getting the same error in that case).

--- Additional comment from Federico Simoncelli on 2015-11-30 07:33:37 EST ---

I have the feeling that this may reproduce with "Utilization" as well (not just "Timeline"). Can you test that as well? Thanks.

--- Additional comment from Dafna Ron on 2015-11-30 07:46:57 EST ---

(In reply to Daniel Korn from comment #3)
> There should be another step: "select a random pod" between 3 and 4, right
> Dafna (I was getting the same error in that case).


Yes :) I think that you have to select the pod to get to the timeline :) sorry for not writing that.

--- Additional comment from Dafna Ron on 2015-11-30 08:55:17 EST ---

(In reply to Federico Simoncelli from comment #4)
> I have the feeling that this may reproduce with "Utilization" as well (not
> just "Timeline"). Can you test that as well? Thanks.

Utilization is not working to begin with (just select it and get an error)

Will add the log for that but I think it was a bug that was already opened? 


Unexpected error encountered

Errors in Management Engine can be caused by:

① Accessing Management Engine from multiple tabs or windows of the same browser on a single machine. Close any duplicate browser sessions, then select a menu option above.
② Pressing the back button during a session.
      Close any duplicate browser sessions, then select a menu option above.
③ An internal system error.
      Please contact your administrator for assistance.


Error text:

Action not implemented [container/x_button]

--- Additional comment from Dafna Ron on 2015-11-30 09:00 EST ---



--- Additional comment from Daniel Korn on 2015-11-30 09:50:43 EST ---

thanks Dafna, and it's true one needs to select a specific pod (or other entity in general). Anyway, I'm working on it.

(In reply to Dafna Ron from comment #6)
> Utilization is not working to begin with (just select it and get an error)

I fixed the utilization for containers last week: https://bugzilla.redhat.com/show_bug.cgi?id=1283683

--- Additional comment from Daniel Korn on 2015-12-01 03:26:03 EST ---

proposed fix: https://github.com/ManageIQ/manageiq/pull/5647

--- Additional comment from Federico Simoncelli on 2015-12-02 04:33:07 EST ---

Comment 2 Daniel Korn 2015-12-07 16:21:10 UTC
The crash occurs when pressing the reload button when in a container Timelines or Utilization.

I can try to find a hack for this issue or I can refactor the container controller so that all the operations will go through the right methods (x_button). Federico, what is your opinion?

Comment 3 Daniel Korn 2015-12-08 14:27:54 UTC
(In reply to Daniel Korn from comment #2)
> The crash occurs when pressing the reload button when in a container
> Timelines or Utilization.

please ignore this comment, it is related to https://bugzilla.redhat.com/show_bug.cgi?id=1287563 (similar title).

Comment 6 errata-xmlrpc 2016-02-10 15:21:19 UTC
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:0159


Note You need to log in before you can comment on or make changes to this bug.