Bug 1466172
| Summary: | [RFE] add graph refresh support for RHV full refresh | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Oved Ourfali <oourfali> |
| Component: | Providers | Assignee: | Piotr Kliczewski <pkliczew> |
| Status: | CLOSED ERRATA | QA Contact: | Angelina Vasileva <anikifor> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.8.0 | CC: | dajohnso, gblomqui, jfrey, jhardy, obarenbo, simaishi |
| Target Milestone: | MVP | Keywords: | FutureFeature |
| Target Release: | 5.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | rhev, Graph refresh | ||
| Fixed In Version: | 5.9.0.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-01 13:14:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | RHEVM | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Oved Ourfali
2017-06-29 08:17:17 UTC
Full refresh measurements for CFME-5.9.0.14/RHV-4.2.1 - scale (1800 VMs, 400 Hosts), both systems on same location (no high latency): * Initial full refresh (Right after connecting the RHV to CFME) Graph Refresh - OFF - 4.5 min Graph Refresh - ON - 4.5 min * Second full refresh (Running Refresh Relationship, after RHV is connected, and the initial full refresh has ended) Graph Refresh - OFF - 3 min Graph Refresh - ON - 2 min Removing the bugs from depends on as those do not block the Graph refresh feature. Added a separate bug tracker or this purpose: Bug 1532255 - [Tracker][RHV] Graph Refresh bugs Moving to Verified as Automation full test list showed no regression on CFME with RHV Graph refresh switched ON, compared to same tests run with Graph Refresh switched OFF. Tested on CFME-5.9.0.16/RHV-4.1.8.2 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-2018:0380 |