Bug 1628726
| Summary: | [RFE] - Containers Overview page Status cards do not load without provider | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Mike Shriver <mshriver> | ||||
| Component: | UI - OPS | Assignee: | Harpreet Kataria <hkataria> | ||||
| Status: | CLOSED ERRATA | QA Contact: | juwatts | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 5.10.0 | CC: | hkataria, juwatts, lavenel, mpovolny, obarenbo, simaishi, smallamp | ||||
| Target Milestone: | GA | Keywords: | FutureFeature | ||||
| Target Release: | 5.10.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | ui | ||||||
| Fixed In Version: | 5.10.0.16 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-02-07 23:03:43 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: | |||||||
| Attachments: |
|
||||||
This is currently working as designed. As discussed with Brad, need to change this into an RFE and show "No Providers found" message on screen when there are no Container Providers in VMDB, we should not try to draw any of the charts on the Container Overview dashboard. ~Harpreet I don't think this qualifies as an RFE, as the screen appears broken in the current state when no providers are displayed. Why not draw the aggregate status cards with 0 count instead of making it a special case? Setting alerts to a special case and div class in the markup when there are no alerts present is already causing problems with automation of this page, handling providers in the same way will just cause more inconsistency for the end user (and for QE automation) New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/63fe84624f7e6a6817621423cf5d4d545985b381 commit 63fe84624f7e6a6817621423cf5d4d545985b381 Author: Harpreet Kataria <hkataria> AuthorDate: Tue Sep 18 15:52:14 2018 -0400 Commit: Harpreet Kataria <hkataria> CommitDate: Tue Sep 18 15:52:14 2018 -0400 Fixed to show 0 Provider in aggregate status card Fixed to show 0 Provider in aggregate status card when there are Providers available in db Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1628726 app/assets/javascripts/controllers/ems_container_dashboard/aggregate_status_card_controller.js | 22 +- 1 file changed, 13 insertions(+), 9 deletions(-) Tested in CFME 5.10.0.16.20180919151347_a0c9e02 The Containers Overview dashboard now shows aggregate status boxes with 0 count for Providers, and provider sub resource types (nodes, containers, registries, etc) 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/RHSA-2019:0212 |
Created attachment 1483152 [details] screenshot of spinners on overview page Description of problem: When no container provider is configured, the Container Overview page displays spinners for the Aggregate Status Card widgets. If a provider is configured, the cards render correctly. After the provider is removed, the cards go back to spinners Version-Release number of selected component (if applicable): 5.10.0.14.20180831154906_2f9a1dd Chrome Version 69.0.3497.81 (Official Build) (64-bit) How reproducible: 100% Steps to Reproduce: 1. Configure 5.10.0.14 CFME appliance 2. Navigate to Compute -> Containers -> Overview through the vertical nav Actual results: Note the spinners instead of aggregate status card widgets Expected results: Status card widgets with titles and 0 counts Additional info: The DOM for these aggregate status cards deviates from the patternfly reference DOM in ways that make the widgets inconsistent for automation. I'd like to discuss an RFE for keeping these widgets more in line with the patternfly reference, or at least making them better for automation.