Bug 1581817
Summary: | [RFE] Can Not Create VM Chargeback Reports with CPU Cores Rate | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | myoder |
Component: | UI - OPS | Assignee: | Hilda Stastna <hstastna> |
Status: | CLOSED ERRATA | QA Contact: | Nandini Chandra <nachandr> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.8.0 | CC: | cpelland, hkataria, hstastna, jdupuy, jocarter, lavenel, lpichler, mfeifer, mpovolny, myoder, nachandr, ngupta, obarenbo, pjakobs, pwallend, simaishi |
Target Milestone: | GA | Keywords: | FutureFeature, RFE |
Target Release: | 5.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.11.0.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-12 13:33:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | Bug | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: |
Description
myoder
2018-05-23 16:43:18 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/01d2a9a12b9ba000a12fbe374ba28232a62299d6 commit 01d2a9a12b9ba000a12fbe374ba28232a62299d6 Author: Hilda Stastna <hstastna> AuthorDate: Tue Apr 2 08:25:08 2019 -0400 Commit: Hilda Stastna <hstastna> CommitDate: Tue Apr 2 08:25:08 2019 -0400 Display info about unavailable fields while editing report Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1581817 app/controllers/report_controller/reports/editor.rb | 13 + app/views/report/_form_columns.html.haml | 6 + 2 files changed, 19 insertions(+) Verified in CFME 5.11.0.11 Steps of verification: https://github.com/ManageIQ/manageiq-ui-classic/pull/5418 Verified that unavailable fields are showing in the caution message. 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-2019:4199 |