Bug 1372318 - On container dashboard - StatusBox population is delayed
Summary: On container dashboard - StatusBox population is delayed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Ari Zellner
QA Contact: Gilad Shefer
URL:
Whiteboard: container:dashboard
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 12:11 UTC by Gilad Shefer
Modified: 2018-06-06 11:39 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-20 17:43:02 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:


Attachments (Terms of Use)

Description Gilad Shefer 2016-09-01 12:11:39 UTC
Description of problem:


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


How reproducible:

sel.force_navigate('container_dashboard')
sb = StatusBox('Nodes')
sb.value() # -> 0 - return zero even it isn't

Steps to Reproduce:
1. Run the above lines in the automation framework
2.
3.

Actual results:
0

Expected results:
The value

Additional info:

IMPORTANT NOTE: this bug could be skipped if we put short time.sleep before StatusBox initialization.

Comment 2 Jaroslav Henner 2016-09-01 13:04:52 UTC
Can we get "N/A" or something like that before the page loads the data from
https://APPLIANCE_IP/container_dashboard/data
?

Comment 3 Ari Zellner 2016-09-08 15:23:45 UTC
Is that a solution? You will still need to see that the actual number appears after x seconds

Comment 4 Federico Simoncelli 2016-09-15 15:02:45 UTC
Can you give more information on the bug?

The information are populated asynchronously in the page and we'll see this being more and more used going forward.

Comment 5 Jaroslav Henner 2016-09-16 09:54:11 UTC
(In reply to Ari Zellner from comment #3)
> Is that a solution? You will still need to see that the actual number
> appears after x seconds

Yes, but as long as the non-yet-updated status is 0, we cannot differentiate between the updated and not updated state.

We want to poll as long as we see something like N/A. We cannot poll as long as we se 0 because it might be the correct (updated) number of items.

Comment 6 Federico Simoncelli 2016-09-16 16:02:11 UTC
(In reply to Jaroslav Henner from comment #5)
> We want to poll as long as we see something like N/A. We cannot poll as long
> as we se 0 because it might be the correct (updated) number of items.

OK for me to use a "N/A" or a dash "-" before real data is actually loaded.

Comment 7 Ari Zellner 2016-09-19 12:56:22 UTC
Upstream PR: https://github.com/ManageIQ/manageiq/pull/11359

Comment 9 Einat Pacifici 2017-02-07 11:58:33 UTC
Moved to verified. This is no longer an issue.


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