Bug 1291757
Summary: | CFME allows deletion of default compute and storage chargeback rates | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
Component: | UI - OPS | Assignee: | Greg Piatigorski <gpiatigo> |
Status: | CLOSED ERRATA | QA Contact: | Nandini Chandra <nachandr> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 5.4.0 | CC: | dajohnso, dclarizi, gpiatigo, hkataria, jhardy, jocarter, jprause, mfeifer, mpovolny, nachandr, nobody, obarenbo, simaishi |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.5.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | chargeback | ||
Fixed In Version: | 5.5.5.0 | Doc Type: | Bug Fix |
Doc Text: |
In the previous version of CloudForms Management Engine, it was possible to delete the default compute and storage charge back rates, and there was no way to recover the default rates after deletion. This bug was fixed by renaming default rates to sample rates, allowing them to be copied, edited, deleted, and changing code so that any rate that is currently in use can not be deleted. The default compute and storage chargeback rates can no longer be deleted in the new version of CloudForms Management Engine.
|
Story Points: | --- |
Clone Of: | 1206285 | Environment: | |
Last Closed: | 2016-07-26 15:30:36 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: | |||
Bug Depends On: | 1206285 | ||
Bug Blocks: |
Comment 3
Greg Piatigorski
2016-02-19 21:05:34 UTC
MR re-created, code fix should be there. We do need to change doc text, per my note above, to reflect new business rule. MR: https://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/938 Verified that assigned Compute and Storage rates cannot be deleted. Verified in 5.5.5 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://rhn.redhat.com/errata/RHBA-2016-1488.html |