| Summary: | On container dashboard - StatusBox population is delayed | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Gilad Shefer <gshefer> |
| Component: | UI - OPS | Assignee: | Ari Zellner <azellner> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Gilad Shefer <gshefer> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | azellner, bazulay, cpelland, dajohnso, epacific, fsimonce, gshefer, hkataria, jhardy, jhenner, mpovolny, obarenbo, simaishi |
| Target Milestone: | GA | ||
| Target Release: | cfme-future | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | container:dashboard | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-20 17:43:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | Container Management | Target Upstream Version: | |
Can we get "N/A" or something like that before the page loads the data from https://APPLIANCE_IP/container_dashboard/data ? Is that a solution? You will still need to see that the actual number appears after x seconds 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. (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. (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. Upstream PR: https://github.com/ManageIQ/manageiq/pull/11359 Moved to verified. This is no longer an issue. |
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.